dsoutherland
Programmer
- Feb 26, 2004
- 15
- 0
- 0
I have a weird problem with a VB6 app that fronts an Access 2000 database. Occaisionally, a user will experience a record lock on a table when a new record is being created. The message indicates the machine that has the table locked and it has always been the same machine. That user on the offending machine usually has no record accessed in the application, but the application is active. The user on the offending machine can close the application and the user trying to save the new record is successful. This has been going on for a couple of years and it began when I installed a new PC for that user (WinXP). I have tried everything in the world to correct it. I have even clean-installed XP on that machine and the record locks still occur. Recently, however, I had to replace a different PC in the network, and I replaced it with one that had seen service in the network before with no problems. Now we occaisionally get a record lock where that machine is the offender. The only eveidence I can find that something is different with those two machines is looking at the open files count from the server (W2K Server). The database is always opened with a multiple (ususally more than 3) file count.
Any ideas?
Thanks!
Dwight Southerland
Any ideas?
Thanks!
Dwight Southerland