New errors after servicepack 3

[safirlaila]

We use Pdox9 and our customers then have Pdox 9 Runtime. After more and more of them have installed Windows XP we more often get the problems with GP-messages when starting Pdox Runtime. The solution to this problem is to install the servicepack 3.

BUT : Our application has reports where the query behind refers to the private directory. The table in the query is of course in the working directory. (This is done because multiple users then can have different choices in the report at the same time)

We then get the error message where the program can´t find the table in the query. It looks for it in the private directory. The temporary (but bad) solution to this is to have two icons, one with the private directory set to the same directory as the working directory and the second with the private directory to for example C:\WINDOWS\TEMP.

Using the second icon will cause the message 'Directory is busy' if more than one user uses the application.

Has anyone got any experience with this? Grateful for answers.

 

[footpad]

safirlaila,

It sounds as if your BDE settings were reset by the Service Pack. Verify that each workstation:

1) Sets a specific (and private) setting for the NET DIR Paradox driver setting in BDE Admin. This can be the same as the user's TEMP directory.

2) That all users have full (read/write/update/delete) rights to the NET FILE folder on the the network.

In addition, you may be interested in the following articles on my website:

--

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

talks about common errors you run into when setting up Paradox for a network.

--

http://techtricks.com/paradox/setnetfile.php

shows how to set the NET FILE location using BDE Admin. This needs to be done for each Paradox user.

--

http://techtricks.com/paradox/cmdline.php

describes Paradox's command-line options, including -p (which lets you set the private directory from the Paradox shortcut).

In addition, you might also take a peek at

http://mirwin.homestead.com/files/faqs/WinNetFileRules.html,

which is based on the standard FAQ on the subject.

Hope this helps...

-- Lance



Hoipe this helps...