How to change the registry-properties
ExclusiveAsyncDelay
FlushTransactionTimeout
ImplicitCommitSync
Lock Delay
LockRetry
MaxBufferSize
MaxLocksPerFile
PageTimeout
RecycleLVs
SharedAsyncDelay
Thread
UserCommitSync
in a way getting a maximum of stability?
I' d like to use VBA like
DBEngine.SetOption dbImplicitCommitSync, true
but there is no offline or online documentation on the registry settings concerning best stability: Which values are recommended, are neccessarry and are critical?
Background:
I'm currently working on a rather big database being used in a multiuser network at WinNT4 SP5 (!) and actually - we won over SAP! ("Why re-programming everything in SAP, Acc is much cheaper!")
Yet stability is still an issue and needs to be improved, because 2 or 3 concurrent users repeatedly got errors while DAO.VBA-code inserts records into a table, reads contents which (then) are updated and by then does not return enough inserted records whenever a second user reads that table.
On the MS-site there hasn't been any KB-article concerning one of these settings and other KBs are not enlightening either.
Anybody can help?
Thanks a lot!
Michael Haussmann-Moser
ExclusiveAsyncDelay
FlushTransactionTimeout
ImplicitCommitSync
Lock Delay
LockRetry
MaxBufferSize
MaxLocksPerFile
PageTimeout
RecycleLVs
SharedAsyncDelay
Thread
UserCommitSync
in a way getting a maximum of stability?
I' d like to use VBA like
DBEngine.SetOption dbImplicitCommitSync, true
but there is no offline or online documentation on the registry settings concerning best stability: Which values are recommended, are neccessarry and are critical?
Background:
I'm currently working on a rather big database being used in a multiuser network at WinNT4 SP5 (!) and actually - we won over SAP! ("Why re-programming everything in SAP, Acc is much cheaper!")
Yet stability is still an issue and needs to be improved, because 2 or 3 concurrent users repeatedly got errors while DAO.VBA-code inserts records into a table, reads contents which (then) are updated and by then does not return enough inserted records whenever a second user reads that table.
On the MS-site there hasn't been any KB-article concerning one of these settings and other KBs are not enlightening either.
Anybody can help?
Thanks a lot!
Michael Haussmann-Moser
Last edited:
