Clipper on a network : when server wents down
M Mordkovych
can be?
TIA
Stephen Quinn
> Hi! Program freezes when Novell server occasionaly goes down. What
> solution can be?
Define 'goes down'.
Assuming power failure - put the Server on a UPS.
CYA
Steve
M Mordkovych
I dont think it's power failure. Probably it's just connection to server
that is lost.
Thanks, I know about UPS
"Stephen Quinn" <stev...@SPbigpond.AMnet.au> wrote in message
news:1sbdk.18449$IK1....@news-server.bigpond.net.au...
N:dlzc D:aol T:com (dlzc)
"M Mordkovych" <m_mordk_...@verizon.net> wrote in message
news:_zedk.1148$Ae3.152@trnddc05...
> "Stephen Quinn" <stev...@SPbigpond.AMnet.au> wrote in message
> news:1sbdk.18449$IK1....@news-server.bigpond.net.au...
>>
>>> Hi! Program freezes when Novell server occasionaly
>>> goes down. What solution can be?
>>
>> Define 'goes down'.
>>
>> Assuming power failure - put the Server on a UPS.
> I dont think it's power failure. Probably it's just
> connection to server that is lost.
> Thanks, I know about UPS
Switch to (x)Harbour and run the connections under terminal
services (I don't know if Clipper can do this too).
Switch to xHarbour and run SQLRDD... probably more tolerant for
flaky network connections.
Keep local copies of all data / index files, and only allow
read-only access when the connection is down.
Quit trying to data intensive applications with a DOS program
over a flaky network architecture. Like wireless. Just because
you have the best network software running, doesn't mean that DOS
is that good.
David A. Smith
AUGE_OHR
> Probably it's just connection to server that is lost.
what OS() and which Novell Server / Client Version ?
show us AUTOEXEC.NCF (from NW Server)
greetings by OHR
Jimmy
Stephen Quinn
> I dont think it's power failure.
If you don't know what the problem is how are we to advise you??
You should find out before asking us questions on how to fix it.
> Probably it's just connection to server that is lost.
Then they may have bad NICs/cables.
CYA
Steve
M Mordkovych
1) Can you explain what terminal services are?
2) Please define "probably more tolerant" - is it going to help?
What effort is involved in swicthing to (x)Harbour a big Clipper application
with some libraries used?
Thanks
"N:dlzc D:aol T:com (dlzc)" <dl...@cox.net> wrote in message
news:Xjfdk.3143$tN1....@newsfe17.phx...
sali
grupi:0Z4dk.1090$Ae3.778@trnddc05...
> Hi! Program freezes when Novell server occasionaly goes down. What
> solution can be?
maybe bad error handling?
there must be read/write error [possibly with timeout] on network device
when connection lost [for whatever reason: server breaks or connection
breaks]
so, the best thing is to correct the app?
M Mordkovych
Yes, that's exactly what I am looking for! So the question is : how to
provide elegant error handling?
Regards,
"sali" <sa...@euroherc.hr> wrote in message
news:g54kv8$gbh$1...@ls5.tel.net.ba...
dlzc
On Jul 9, 9:27 pm, "M Mordkovych" <m_mordk_no_sp...@verizon.net>
wrote:
...
> > Switch to (x)Harbour and run the connections
> > under terminal services (I don't know if
> > Clipper can do this too).
> 1) Can you explain what terminal services are?
The application runs on a terminal server (with a better connection).
Your customers communicate with the application over the network.
http://www.microsoft.com/windowsserver2003/technologies/terminalservices/default.mspx
Kind of like having each user connect via PC Anywhere, only they all
talk to the same computer.
> > Switch to xHarbour and run SQLRDD...
> > probably more tolerant for flaky network
> > connections.
> 2) Please define "probably more tolerant" -
> is it going to help? What effort is
> involved in swicthing to (x)Harbour a big
> Clipper application with some libraries
> used?
"Probably more tolerant" means that the data being sent over the link
is simply the handful of records you ask to see. Your computer does
not maintain the indexes (hard to trap), or do the grunt work of data
sifting... the remote server does that.
The Clipper or Clipper Tools code goes straight over to xHarbour.
There are a (very) few 3rd party libs that have been recreated in
source, so that they can be compiled into 32- or 64-bits native
WinDoze applications
> Thanks
It looks like "sali" can give you some good hints for Clipper in
improving "time outs" and error trapping. I think the problem is that
WindDoze doesn't tell its DOS-box anything about network problems in a
timely fashion... and DOS code will just wait...
David A. Smith
sali
grupi:912c7bbd-36da-429d...@k37g2000hsf.googlegroups.com...
Dear M Mordkovych
> It looks like "sali" can give you some good hints for Clipper in
> improving "time outs" and error trapping. I think the problem is that
> WindDoze doesn't tell its DOS-box anything about network problems in a
> timely fashion... and DOS code will just wait...
well, i checked the old c52 [or c53] dbu utility, inside win/xp dosbox,
ethernet tcp/ip network, remote volume mapped with "net use *":
1] dbf resident on server, browsing with dbu.
2] unplugging network cable [on the server side, so the workstation is still
connected to network]
3] few seconds nothing happens, dbu is waiting something
4] then throws alert error dbfntx/1010 read error
i think this timeout is ok, since netwotk must survive few seconds of being
unplugged before declaring lost of connection
N:dlzc D:aol T:com (dlzc)
"sali" <sa...@euroherc.hr> wrote in message
news:g5k5ck$9id$1...@ls5.tel.net.ba...
> "dlzc" <dl...@cox.net> je napisao u poruci interesnoj
> grupi:912c7bbd-36da-429d...@k37g2000hsf.googlegroups.com...
...
>> It looks like "sali" can give you some good
>> hints for Clipper in improving "time outs" and
>> error trapping. I think the problem is that
>> WindDoze doesn't tell its DOS-box anything
>> about network problems in a timely fashion...
>> and DOS code will just wait...
>
> well, i checked the old c52 [or c53] dbu utility,
> inside win/xp dosbox, ethernet tcp/ip network,
> remote volume mapped with "net use *":
>
> 1] dbf resident on server, browsing with dbu.
> 2] unplugging network cable [on the server side,
> so the workstation is still connected to network]
> 3] few seconds nothing happens, dbu is waiting
> something
> 4] then throws alert error dbfntx/1010 read error
>
> i think this timeout is ok, since netwotk must
> survive few seconds of being unplugged before
> declaring lost of connection
I am sorry that I made you go through this effort. I think the
OP hinted he wanted to know more about error trapping in Clipper.
I found this style guide:
http://www.ghservices.com/gregh/clipper/
... and this pointer to an article that may be found at a
library:
http://www.accessmylibrary.com/coms2/summary_0286-9287346_ITM
... and maybe this isn't too old:
http://www.leylan.com/app.asp?pg=evolve
David A. Smith