Windows 2000 and Network Control file.

[jiminy]

I used to have Windows 95 and was using Pdox9. Now I have a new machine with windows 2000 Professsional. I store the Pdox files on two network-type directories. I can access one directory but not the other. The error msg says the "directory is controlled by another .net file", and then lists the pdoxusers.lck file in the directory I am unable to use.
Our network administrator says that Pdox doesn't like it when files aren't all in the same directory and the problem is with Paradox. So why didn't I have this problem with Win95??
Will the 2000 patch solve this problem? If so, I will post my email address, if someone will be so kind as to send it.
Other ideas?

 

[footpad]

Jiminy,

For some background on the actual error, take a peek at a set of articles on my site. (Start with

http://techtricks.com/paradox/netinit.php3

and then review the Related articles for ideas on how to resolve the problem.)

Your network admistrator appears to be missing a couple of key facts:

1. Paradox can handle tables stored in different directories, provided everything is properly configured.

2. You should be using one PDOXUSRS.NET if at all possible. unless you have more than 300 simultaneous users or have people who travel (and therefore cannot be connected to the network), this should not be an issue.

3. Paradox (the software0 doesn't control the locks; BDE does. It's a bit like trying to blame Access for ODBC connection problems. Sure, you can do that if you like, but it's more productive to find the actual solution rather than fixing blame. IMHO, of course. YMMV.

4. I've not seen this magical patch referred to in the other thread. All formal patches are freely available from Corel's web site or Borland's. While there are certain configuration settings required for older versions of Paradox under Windows 2000 (and other NT variants), I'm not aware of any third-party software that helps 32-bit versions of Paradox. and would be leery of any claims to the contrary. But, that's just me and my security-concious paranoia.

5. There's a good FAQ on Paradox/BDE network setup available at

http://www.thedbcommunity.com/faq/13.htm;

you may find other helpful tips in the other FAQ's available there.

Hope this helps...

-- Lance

 

[JBirdieH]

We have upgraded to Pdox10 from 9 and regularly among all clients (win95,nt,2000) have problems starting paradox. It seems that lck files in the private directories are intermitently(but often) not deleted upon exit of paradox. The next attempt to run begins the error messages. (someone else is controlling the file etc.) Is this a known problem or is there an additional step to take in the configuration of the clients/server that can prevent this (in a global sense, I know I can just delete the lck files) There has also been a rise in the instance of local .net files. There isn't anything the matter with the server, it is always up. Could there be a timing issue?