Boris wrote:
Brendan Reynolds wrote:
I wouldn't usually do this, but curiosity got the better of me, and I
took a look at the MDB you posted. I noticed that the error doesn't
occur if I open and close the form without clicking the command
button. It occurs only after clicking the button, the code behind
which writes a record to a table and then deletes that same record.
This leads me to suspect that we're seeing some kind of timing or
caching problem. If this were DAO, I'd be thinking about putting in a
couple of DbEngine.Idle statements, one after the line that writes
the record and another after the line that deletes it. But I don't
know what, if anything, the ADO equivalent of DbEngine.Idle might be?
Hi, thanks for jumping into the thread! I will rewrite the code using
DAO. Maybe this is an ADO problem. I will be back soon.
I'm back: I didn't change the code but removed one table and the subform.
Now there is just one table and just one form - the runtime error persists.
See the attachment please.
Boris
|