We have several customers using our system. The system runs fine for them all, except recently, when one sufferred from a "Lock Count Exceeded" error. They were running a process which dealt with updating data against 10,000 records. They have a Novell network (I know about the Novell limitations/defaults etc), BUT the system and it's database(s) are all resident on a single client machine's C drive, so that will surely eliminate Novell from the equation??
Splitting the data into a batch of 1500 records, then a batch of 8500 resulted in the process running error free.
Before diving in to change the MaxLocksPerFile setting within the Windows registry (they are running Windows 2000), we got them to send us their data, and testing it on one of our machines resulted in the process in question running error free. The MaxLocksPerFile setting on our machine (also Windows 2000) is the same default setting of 9500 as is set on theirs.
Why would the process work on our machines without error, yet repeatedly fire the "Lock Count Exceeded Error" on theirs? Even though the process is all local to the client machine (on the C drive) could Novell be affecting it in any way?
Also let's say we change the Windows registry MaxLocksPerFile setting to 20,000. Will such errors be fired off again if theprocess involves 20,001 records at some point in the future?
If anybody has any thoughts, experiences with this aspect of Access, I'd be very grateful for any feedback.
Thanks.
Splitting the data into a batch of 1500 records, then a batch of 8500 resulted in the process running error free.
Before diving in to change the MaxLocksPerFile setting within the Windows registry (they are running Windows 2000), we got them to send us their data, and testing it on one of our machines resulted in the process in question running error free. The MaxLocksPerFile setting on our machine (also Windows 2000) is the same default setting of 9500 as is set on theirs.
Why would the process work on our machines without error, yet repeatedly fire the "Lock Count Exceeded Error" on theirs? Even though the process is all local to the client machine (on the C drive) could Novell be affecting it in any way?
Also let's say we change the Windows registry MaxLocksPerFile setting to 20,000. Will such errors be fired off again if theprocess involves 20,001 records at some point in the future?
If anybody has any thoughts, experiences with this aspect of Access, I'd be very grateful for any feedback.
Thanks.