DEO - LAN problem

I have a fairly large app a client is running on Win2003 Server /
Terminal Server and XP workstations 

The app use DEO

There seems to be a problem with the LAN connection going dead

Frequently when starting from the shortcut icon they get a file not
found error on the first call to the DEO object. It also happens when
a form sits idle for any length of time.

The startup program traps the first instance with a Try/Catch and
displays an error message. On the next try everything is okay

I'm at a loss  for trapping the second instance as it can happen in
any form and in any place in the process

Any suggestions would be appreciated

Thanks

In article <btilv31hlha2pkd0tq9n12b8uhpee8a4qr@4ax.com>, 
fpolan@pcassist.on.ca says...
> I have a fairly large app a client is running on Win2003 Server /
> Terminal Server and XP workstations 
> 
> The app use DEO
> 
> There seems to be a problem with the LAN connection going dead
> 
> Frequently when starting from the shortcut icon they get a file not
> found error on the first call to the DEO object. It also happens when
> a form sits idle for any length of time.
> 
> The startup program traps the first instance with a Try/Catch and
> displays an error message. On the next try everything is okay
> 
> I'm at a loss  for trapping the second instance as it can happen in
> any form and in any place in the process
> 
> Any suggestions would be appreciated
> 
> Thanks
> 
> Frank Polan


Frank,

How many DEO folders do you have? One thought would be to duplicate each 
folder you have so that if DEO cannot find the first copy, hopefully the 
second copy will be in a location that can be reached.

-- 
Geoff Wass [dBVIPS]
Montréal, Québec, Canada

.|.|.|        dBASE info at http://geocities.com/geoff_wass       |.|.|.
.|.|.| ---------------------------------------------------------- |.|.|.

Geoff

Just one DEO folder - on the Win 2003 server
It can always be reached  -  it just needs some sort of "wake up
call"
As I mentioned,  I've fixed the start up problem - I just don't know
how to apply it after that.

If the rowset or variable gets a "not found" error the program
crashes
before I can is use a "wake up" to reestablish the connection

Thanks

Frank


On Tue, 8 Apr 2008 02:25:20 -0400, Geoff Wass [dBVIPS]
<gswassREMOVE_ME@attglobal.net> wrote:

>In article <btilv31hlha2pkd0tq9n12b8uhpee8a4qr@4ax.com>, 
>fpolan@pcassist.on.ca says...
>> I have a fairly large app a client is running on Win2003 Server /
>> Terminal Server and XP workstations 
>> 
>> The app use DEO
>> 
>> There seems to be a problem with the LAN connection going dead
>> 
>> Frequently when starting from the shortcut icon they get a file not
>> found error on the first call to the DEO object. It also happens when
>> a form sits idle for any length of time.
>> 
>> The startup program traps the first instance with a Try/Catch and
>> displays an error message. On the next try everything is okay
>> 
>> I'm at a loss  for trapping the second instance as it can happen in
>> any form and in any place in the process
>> 
>> Any suggestions would be appreciated
>> 
>> Thanks
>> 
>> Frank Polan
>
>
>Frank,
>
>How many DEO folders do you have? One thought would be to duplicate each 
>folder you have so that if DEO cannot find the first copy, hopefully the 
>second copy will be in a location that can be reached.

Andre

see below

On Tue, 08 Apr 2008 14:49:48 +0200, Lysander <nobody@nowhere.de>
wrote:

>Frank J. Polan schrieb:
>> It can always be reached  -  it just needs some sort of "wake up
call"
>> As I mentioned,  I've fixed the start up problem - I just don't know
>> how to apply it after that.
>> 
>> If the rowset or variable gets a "not found" error the
program crashes
>> before I can is use a "wake up" to reestablish the
connection
>
>Frank,
>where exactly is the application running. On the clients or on the 
>server? Do you use the terminal services for this, or is it just a 
>"remote exe" (which then by windows is loaded to the client and
executed 
>there...)
In the main office the app is running on the client PCs; in the 2
branches it's running via TS
It uses DEO (located on the Win2003 server) - only the start up
program/BDE//Runtime are installed on the PCs and TS
>
>If it is the same app for which you needed the Info on the remote 
>client's name, I know it is run by terminal services.
Yes, it's the same one. I still have your message saved. With all the
problems the dropped connections are causing, plus a rash of "memory
access violation" errors seemingly related report to printing I
haven't got back to it yet.
>
>If so, how do you reach the DEO objects? WebDAV, file-share?
>Are you using UNC or named shares or IP-Adresses?
The INI [objectPath] points to a mapped drive. I've tried both a
mapped drive & an IP address in the BDE Alias
>
>You might just have to set your terminal server so that a connection to 
>a file share is detached later than usual.
>
>TS has quite strict and short timeouts until a connection is detached by 
>default. Otherwise opened but unused connections would cost too many 
>resources.
>
>You should consult the TS documentation on how to prolong this
detach-timer.
I'm not the client's IT person so I guess I'll have to talk to him
about. Note that it also seems to be happening on the PC to Server
connections.

I was going to test using a timer object this morning to periodically
check for a file on the server and so "wake up" the connection. Do
you
think this is feasible?

By the way, I've been watching your C# lessons. I wish I wasn't to old
to learn a new languge<g>  A strongly typed, forced declaration,
language like C# would have saved me a lot of time over the years

Thanks

Andre

Not too old - just too old to take on any new projects Once I get this
last app relatively bug free I can enjoy my retirement<g>

Yes, the timer is just a temporary "band aid". I'm going to talk to
my
client's IT about doing something about the dropped connections.

Thanks

Frank Polan

On Tue, 08 Apr 2008 18:18:21 +0200, Lysander <nobody@nowhere.de>
wrote:

>Frank J. Polan schrieb:
>> By the way, I've been watching your C# lessons. I wish I wasn't to old
>> to learn a new languge<g>  A strongly typed, forced declaration,
>> language like C# would have saved me a lot of time over the years
>
>You are definitely not too old, as long as you have a keyboard and some 
>fingers to type on it. If you find the time, try reading the C# steps 
>one after another and you will probably find that it is not THAT 
>complicated.
>
>And, yes, though it seems like "uncomfortable", the impression is
wrong: 
>strongly typed declarative syntax is not really uncomfortable, it is 
>indeed very comfortable once you got used to it.
>
>If you have an option to find bugs during development or later, already 
>after rolling out your app, what would you chose?
>
>
>About the timer... I don't know if this is a good idea.
>It might bring a small improvement, but not a 100% solution.
>The dBase timer will only fire when the processor is idle.
>
>So it will still happen, maybe less frequently, that you will lose the 
>connection. The solution indeed is to set a parameter in the TS 
>configuration.
>
>You mention that it also happens on the "normal" client PCs.
>I can see this here as well. Happens from time to time. With XP much 
>more frequent than with Win2000.
>
>I remember that also on WinXP you can tweak a registry key to hold 
>connection longer.
>For me this problem is not so pressing anymore because when using an SQL 
>backend, the problem is non-existent.
>