Snap Server & PeachTree

[anthony]

We just installed a Quantum Snap Server. It works great for everything, EXCEPT PeachTree. If one person access the data on the Snap drive, you eventually get an error that someone else is doing this function, etc. I call PeachTree Support ($159.00 for 60 minutes) with no postive results. I called Snap and they said it is possible that their OS is the problem, but they are not working on a fix. I search the internet and there seems to be many issues with PeachTree or Betrieve Databases and OS's like Samba or Snap.

The problem goes away if I move it to a local drive. I can even you MS Peer to Peer with Windows 98. As soon as I put the data on the Snap Server, the error pops up. Must have to do with record locking or something.

Please help!

Anthony

[anthony]

Anyone?

[Rick]

You are right. It sounds like the snap server is not allowing the LCK files (the files that lock others out while you are working in a DAT file) to refresh. They have two settings: on and off. Sounds like some setting in the Snap server is not allowing these things to switch. Unfortuantely, SNAP servers are mostly UNIX based and they are notorious for playing with these. My advice is to search all the LCK files (company.lck, vendor.lck, etc) in your server Datapath, delete them (or move them to a temp folder if the idea makes you uineasy), and go into Peachtree and into the company. The LCK files will be recreated. Sometimes just making new ones will solve these problems.

[anthony]

Thanks, I will try that.

[Rick]

No prob. :) One other thing, if any of the users have anything less than FULL permissions to the shared folder, Peachtree can do some oddball things. Might want to look into that also.