Windows 2000 Feature 1

[ninaj143]

My users have Paradox loaded on their machine and the data files on a server. All of us have a mapped network drive to the same netdir. The problem is in W2K, either after inactivity or just when they log on, there is a red X on the network path. Most users don't check this before they try to access the database and think that Paradox is down. Is there a work around?

 

[footpad]

ninja143,

You might see if Persistant Network Connections has been disabled. For more information, see

http://windows.about.com/library/tips/bltip024.htm,

which shows the registry change that handles this and links to a relevant MSKB article.

FWIW, I've been known to disable persistent connections, as this leads to slow downs the first time the connection is referenced. I have seen uses think Paradox (and other applications) is locked up while Windows is verifying the network connection.

I have a theory, which I've not tested, that it may be possible to refer to the resource before the application needs to, perhaps by opening a table in that directory using a TCursor. The idea, here, would be to open a form saying "One moment, please..." while opening the table.

It's worth a shot.

Hope this helps...

-- Lance

 

[boon58]

I had a similar problem then switched the netdir to use the unc path and that seems to have fixed it.