By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,984 Members | 1,461 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,984 IT Pros & Developers. It's quick & easy.

Subform error

P: n/a
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?

Nov 13 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
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?

Nov 13 '05 #2

P: n/a

"Allen Browne" <Al*********@SeeSig.Invalid> wrote in message
news:43**********************@per-qv1-newsreader-01.iinet.net.au...
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"
Thanks Allen, It's actually an Access 2000 db. The existing db suffers a lot
of 2486 errors and a few corrupt forms. (We're in the process of normalizing
much of the data.) Although I suspect my biggest issue is my approach to
this largely unbound form. The subform is bound to the parent form and has
an unbound pseudo subform. The loading of the unbound data is now working
erratically since I started trapping the 3314 errors. I think I'm going to
have to unbind the entire subform to give me the error trapping I want.

--
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?


Nov 13 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.