Update: while there today, I discovered they have not configured all their xp workstations to have local off in the client configuration on access. We changed those settings today & I will be back out on Friday, but am seriously considering service packing pvsw2000i to sp4 w/hot fixes since xp was barely released when sp3 came out (where they are now). I also noticed last week & today that I couldn't rename the macola user in vbaprj\oe0101.o even after all users were out of the users folder & the pervasive monitor. Also, I tried stopping pervasive services on the server to rename the folder. No dice. Had to actually reboot the server to rename the oe0101.o\macola folder. This was before I found the improper settings on the xp clients.
If anyone else has any thoughts or updates, great. Otherwise, I'll let you know what I find out Friday. Another FYI: not all users get the oeordhdr locked message. I have copied the oe0101.0 vba project to each user macola ID now as I read on another thread that the macola user can cause record locking problems, even tho it saves administrative overhead on maintenance of the vba code. We have about 30 user IDS & 25 concurrent macola users. Server is definitely nt4/sp6, dual processor 1.4 gig w/1 meg memory, but not dual NICs. I did get a Dr Watson memory conflict error today when I rebooted the server after manual shutting off pervasive services prior to reboot. I didn't have users log off their WS, only macola. More later.