Access 2003 crashes on Linked FormSubform with Filter ( 0xc0000005 err msg)

  • Thread starter Thread starter Stephen Haley
  • Start date Start date
S

Stephen Haley

Ive just run into this one and it turned out the filter was the problem. I
had a master form with a text box driven from a combo box. The text box in
turn was declared as the parent link to the subform. When the subform had a
filter in place and I changed the value in the linked text box then Access
crashed (UAE) with the ubiquitous 0xc0000005 error in the debug dump. From
what I can remeber this is simply Access losing internal pointers. The
solution was to turn off the filter (I also removed the filter string to be
safe change the textbox then reapply the filter and it works fine. No idea
why this was happening and could be a result of a cumulation of things eg I
have the form subclassed as well. But just incase any one else runs into
this it might provide a possible solution.

rgds
Stephen
 
Stephen, thank you for posting your experience.

There are several bugs where Filters do not work correctly, e.g.:
http://members.iinet.net.au/~allenbrowne/bug-02.html
but I have not experienced that as the cause of a crash.

In case the problem recurrs, it may be worth considering whether any of
these were the cause of the issue:

1. The find named in LinkChildFields is not represented by a text box on the
subform. This is a bug in Access 2002 and 2003, and it seems to be related
to the AccessField type. You can avoid the bug by adding a text box (hidden
if you like) for your foreign key field, so that the reference is to a
Textbox type.

2. Name AutoCorrect was enabled, and Access was getting confused about what
was what. Frequent cause of crashes and corruptions. Details:
http://members.iinet.net.au/~allenbrowne/bug-03.html

3. Your Filter included a subquery. It's not difficult to crash JET with
these. Alternatives might be to alter the RecordSource of the subform to an
inner join query with the other table (if the join goes toward a lookup). If
you do this programmatically, be sure to set the LinkMasterFields and
LinkChildFields properties again, because Access is likely to assign these
at will.
 
Back
Top