These can be difficult to trace. It is a matter of removing things and
tracking down the culprit. Work on a copy so you can restore the things that
are not the problem later.
Remove the code from the check box.
Are there any calculated controls on the main form that refer to values in
the subform? Temporarily remove them.
What else is happening when the check box is checked?
Does the crash occur only on the new row (when a record buffer is being
assigned)?
Only if the record is being dirtied?
What is the RecordSource for the subform? Query? Calculated fields
contibute? Query with multiple tables? Are you sure the correct fields are
represented (e.g. the foreign key of the related table, if that's the table
you are editing).
What is specified in the MasterLinkFields/ChildLinkFields? Fields?
Calculated text boxes?
Does the subform crash if it is opened on its own (i.e. directly from the
Database window)?
What version of Access? Do you have the latest service pack for your version
of Office AND for JET 4? See support.microsoft.com
--
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.
"Andrew Wrigley" <aw******@yahoo.com> wrote in message
news:f5**************************@posting.google.c om...
Hi
I have what seems a corruption of an mdb that is not solved by the
decompile command line trick.
The problem appears when clicking on a subform control (check box)
that has a event handler associated with it.
Everything works ok, until I click on the check box, whereupon Access
fails with an application error. It appears that execution never
reaches the check box event handler, so I have no way of debugging the
process.
Any suggestions?
Regards
Andrew Wrigley
