Re: Error 3155- Is there no solution?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

If an order is entered, however, and the database closed and reopened or the
user switches to another record and returns, then the problem doesn't occur.

Any help on how to solve this would be apprecated.

Hi Mark,

Rereading your quoted observation gave me a fresh insight. It isn't a lock - it's something within your update code that conflicts with something else sometimes, or possibly bad compilation due to reference conflicts, or ????

What ever the cause - it's certainly a code or interpretation problem if your update code isn't working right, but, (as stated) the form will save changes when you edit or add a record then navigate away from the record so that the form's current record loses focus. That mean's Access's native code that saves the data is working when your code isn't. I don't know exactly why, but given your observation, this appears to be true.

Since the root cause appears to be elusive -
My amended recommendation is do exactly what does work per your stated observation.

On the order entry form - instead of running your current update code - make a 'save order' button
that navigates to a previous record or the first record or whatever, and then returns via a saved bookmark.

Hope this helps...
Gordon

Quantcast