Good luck. I've battled this for nearly two years. One solution you can
use in your app is a timer that accesses a file (or anything) on the
network drive from time to time, whether the user is doing anything or
not. Of course, if your app is shut down, that's not going to help.
Do your users get an error from your application if they simply restart
the app? Or do they have to reboot?
What I haven't gotten to work is using Windows Scripting to reconnect
the drive link. If WS tries to reconnect and the link is still valid
(although "not active" like Ted points out) then you get an error, and
it's unchanged. If you try to drop the connection and then reconnect, it
drops fine and reconnects fine, but the reconnection just gets you back
to where the connection is valid, but not active. In other words, you're
right back where you started.
The one thing that ALWAYS works is to (manually) click the link with the
red x on it in Windows Explorer.
None of the registry changes I've found made any difference in Windows
7. Haven't deployed any apps on Windows 8 yet.
What I would like to find is a "keep alive" app like that available for
Internet connections...where the app runs all the time and pings a URL
every X minutes just to force the ISP to leave the circuit live. I just
want to "poke" the network drive...maybe get a directory listing of the
root folder and then discard the info...every X minutes. Just install it
to run anytime the workstation is active.
Or better yet, move away from shared DBFs to a client-server solution.
That way you have a whole new set of issues!
Mike Copeland
-------- Original Message --------
Subject: Re: Accessing FoxPro Tables on a Server
From: Ted Roche <[email protected]>
To: [email protected]
Date: 1/11/2014 1:52 PM
On Sat, Jan 11, 2014 at 11:06 AM, Jeff Johnson <[email protected]> wrote:
I have several users accessing an application on a server. Two users that
are using laptops lose connection after 10 or 15 minutes of idle time.
They say they have to "completely get out of it and start over" each time.
This is a Windows "feature" in recent Windows OS 7, 9 versions. It order to
"help" the "user" (who is, of course, stupid), Windows benevolently drop
network connections that are idle, regardless of whether there are files
open.
Open a Windows Explorer and see if you can see windows share icons with red
"X" icons superimposed on them. A single-click should make the red X
disappear.
Based on the OS you find, search for "Windows shares time out" should give
you some leads on what needs to be altered on the workstation. I think it's
something like "Windows Networking Discovery" or something benign-sounding
like that.
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
