>>>I have some code that SCANs a large number of records in a table and does some stuff with each record, including a REPLACE. On particularly large tables where a lot of records are processed, the server is giving a message that the record lock threshhold has been exceeded and the computer freezes up. Shouldn't the REPLACE command lock and unlock the records automatically? Why would a series of REPLACES cause a problem?
>>>
>>>Thanks.
>>
>>
Is it Novell ?
>>Cetin
>
>Yes, why?
Sounded like it was server not Fox complaining about locks. A netware server (talking about up to 3.11 - left then) has to place locks into any file that requested to lock some bytes. Well I'm not well enough to explain it. Here is some info copied from MSDN :
"Using ISAMStats with NetWare
If you use Access on a Novell NetWare 3.11 network, then you're probably aware of the limitations NetWare places on the number of record locks that you can place on a given file. In fact, unless you get the patch from Novell to fix this problem, you can crash the server by requesting too many record locks (see the July 1994 issue for more details). Even if you get the patch, you're still limited in the number of locks you can place before the query simply fails (the maximum number this can be set to is 10,000).
One way around this problem is to use the ISAMStats method to determine the number of locks that have been placed. By having your application track how many locks are placed inside a transaction (where the locks won't be released until you use the Commit or Rollback methods), you'll no longer have to "guesstimate" when a query is approaching the limit and instead can use exact figures to determine how many locks have been placed.
There is one limitation to this method. Since a single "Locks released" call can release any number of locks (or all of them), this method will be effective only in a situation like a transaction, where you know that no locks will be freed. This isn't a major problem, however, since large transactions are one of the most common times that NetWare users run into the problem. —Michael Kaplan and Lynn Shanklin"
Currently I can help this far (it has been at least 3 years I dropped Novell).
Cetin
