I have observed exactly the same problem on an XP PRO install today. Nothing seems to fix it. Is there any help yet?

From my research everything points to Peachtree as being very unstable on a network.  Any type of network anomoly can cause a peachtree company to go bad, especially when the company is being written to or read from.  This is due to the structure of the peachtree datafile.  Peachtree is a much better when used on a stand alone machine with and UPS attached for any power outages, giving the user time to close out the company safely.  The makers of Peachtree do make a better product for network accounting, but is used mainly in accounting companies and not for the one company user.  I don't know if this helps, but thought I would let you know of what you are dealing with.  It is very expensive to fix a corrupted peachtree company, and requires the use of Pervasives Betrieve Data engine running as well as some specialized software, I have had to fix a number of peachtree companies and it is no easy task.  In summation Peachtree, as stated before is not made for the network, and as much as Best Software would like to not admitt it those are the facts.

We have been running P\T for 5 years on a network and have had good results. However there are a few areas that need help.

The problem you are having can be solved by adding one more level on the tree, For some reason on the network you need a tree off the root like this z:\peachw\peachw. The way to fix this is add one more level on the z: drive. The path during instalation on the data side can not read z:\. Peachtree seems to need that second level to locate files. You can make a new folder under your Z: peach dir and copy/move your files there then re-install using this new path.