If this is Access 2002 Service Pack 3, the error might be a spuious one.
The Error event of the form might have caught it.
The fact that the error disappeared could be the result of some particular
combination of data and/or sequence of events, and it might recur under the
same circumstances. OTOH, it might have been an insipient corruption, so a
decompile might be in order. Decompile a copy of the database by entering
something like this at the command prompt while Access is not running. It is
all one line, and include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users -
http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"Bill Stock" <Me*@Privacy.net> wrote in message
news:ns********************@rogers.com...
I have a subform which is causing a 3314 (Field can't contain a null value
because required is set to True) error. I solved this problem by trapping
it in the before update event. But then I started getting a "No Current
Record" error. I wanted to see what err number was coming through, so I put
a MsgBox in the subform's error event. But the MsgBox never came up and the
error is now gone.
Is the MsgBox pulling the focus away from the subform and preventing the
error?