Strange runtime error

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello everybody.

I am dealing with a strange error, that it seems not to be very hard to
correct, but I am really curious about the reason why it raises.

I have a bound form with a save button. When the user clicks that button,
the record gets saved by the following statement:

Application.RunCommand acCmdSaveRecord

My records are being saved fine. If the record is new, the Form_AfterInsert
event procedure is executed. This procedure has to perform some checks on the
form's data, and one of those checks consists of filling a bound object frame
control (called bofActa) with a MS Word document template, so that the user
does not need to retype stuff that is the same for all the records. I fill
the bound object frame control by executing the following statement:

Me.bofActa.Action = acOLECreateEmbed

I think my problems start here. By executing this statement, the record gets
dirty. The Form_AfterInsert ends execution painlessly, but the procedure
which has saved the record raises the runtime error 3021 ("No current
record"). Apparently, I cannot figure out what this error message means. All
I can say is that my record is saved well, despite the runtime error.

My guess is that the Application.RunCommand acCmdSaveRecord statement raises
that error if the record remains dirty after trying to save it. Any ideas
about this?

For my purposes, correcting this error was easy: when this error is raised,
all I have to do is to Resume the statement that raised it: that is to say, I
only have to reexecute the Application.RunCommand acCmdSaveRecord statement.

Thank you very much for your kind attention.
Reis Quarteu
 
Reis, your description of the endless loop condition probably does identify
the heart of the problem. Is there a chance of moving your code into
Form_BeforeUpdate, so that the form is not dirtied again as soon as it is
saved? Alternatively, can you move whatever field is dirtying the record
again into a related table so that record can be created/modified without
dirtying the original one again?

There is a condition where Access 2002 SP3 gives a spurious "No current
record" error, but that does not sound like your situation.
 
Hi, Allen!

I followed your advice of moving some code into the Form_BeforeUpdate sub,
and consequently the 3021 runtime error doesn't come up again. I didn't have
to change anything else, and it now work pretty well, in a more elegant way.
Thank you very much for your advice.

Anyway, let me tell you that there was no endless loop in the previous
situation I described in my previous message. When I detected the 3021 error,
I resumed its execution. But now, as I said before, the current record was
not new anymore (because it was correctly saved in the database, despite the
runtime error), so the Form_AfterInsert sub was not fired. As a consequence,
the runtime error did not raise as well.

Greetings from Portugal.
Reis Quarteu.
 
Back
Top