Hi.
Is there a way to prevent this from happening ?
You may increase the max file locks for the current session, so that this
setting isn't permanent, by changing the Jet DBEngine setting. To do so,
open the Immediate Window by opening the VB Editor and typing <CTRL><G>.
Type the following in the Immediate Window, then press <ENTER>:
DAO.DBEngine.SetOption dbmaxlocksperfile, 15000
This setting is only temporary, so don't worry. Try running the query (or
whatever you were doing when you encountered the error message) and if you
get the same error message, then type this command into the Immediate Window
again, but this time increase the number. You may need to do some
experimenting to find how many locks is enough to handle this transaction.
If you'd like instructions on the Window Registry method to make it
permanent, then please see the following Web pages for two methods:
http://support.microsoft.com/default.aspx?id=815281
http://support.microsoft.com/kb/252444/en-us
what effect would that have on
other processes ?
Any process that uses Jet would use the permanent value for the max locks
per file, so if you use the DAO.DBEngine.SetOption method, then no other
processes outside of your current Access session will be affected.
HTH.
Gunny
See
http://www.QBuilt.com for all your database needs.
See
http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact info.
- - -
If my answer has helped you, please sign in and answer yes to the question
"Did this post answer your question?" at the bottom of the message, which
adds your question and the answers to the database of answers. Remember that
questions answered the quickest are often from those who have a history of
rewarding the contributors who have taken the time to answer questions
correctly.
