Access 2003 bugs...

[Atlas]

I have a form with a mainform. When pressing F9 Access crashes with
following error in log:

Faulting application msaccess.exe, version 11.0.5614.0, stamp 3f3c8e3c,
faulting module msjtes40.dll, version 4.0.8618.0, stamp 403430ac, debug? 0,
fault address 0x00009065.

The error occurs on multiples workstatations with deifferent OSes, latest
ADO installed.

It's not the first time that this happens, also had other crashes with no
hint like (

Faulting application msaccess.exe, version 11.0.5614.0, stamp 3f3c8e3c,
faulting module oleaut32.dll, version 3.50.5016.0, stamp 3d6dfa22, debug? 0,
fault address 0x000014f3.

), sometimes had to rearrange complitely the form design to avoid crashes.

Do we have to start MS code, besides ours?

 

[Allen Browne]

Atlas, this is going to sound silly, but give it a try and let us know how
you go.

Most subforms don't have a text box for the foreign key field, but try
adding one. You shrink it down and set its Visible property to No, but
merely the presence of the text box for the field(s) nominated in the
LinkChildFields property of the subform control can make a difference.

 

[Atlas]

Most subforms don't have a text box for the foreign key field, but try

adding one. You shrink it down and set its Visible property to No, but
merely the presence of the text box for the field(s) nominated in the
LinkChildFields property of the subform control can make a difference.

I always have 2 textboxes on my subforms holding foreign key and primary
key. Both visible and disbled.
It may waste space, but users allways have a unique reference to what
they're managing.

So that's defintelly not the case. Must be something else.

Also tried to build a new empty project, import all forms and modules, but
nothing the problem is still there.

 

[Allen Browne]

Okay. Other suggestions:

1. Name AutoCorrect is off?
Details:
http://allenbrowne.com/bug-03.html

2. Corruption?
If this happens with this one particular database, but other databases are
okay, it may be a corruption. Suggestions:
http://allenbrowne.com/ser-47.html

3. Why the requery?
If #1 and #2 do not solve the problem, examine why the need for the F9.
What's changed? Is there any possiblity that the names in
LinkMasterFields/LinkChildFields could be misunderstood (e.g. if you used a
name such as Name, Date, or Section)? Is a RecordSource being reassigned? If
so, Access can crash if a field disappears or changes data type (usually an
issue with calculated fields). Any subqueries? JET can be a bit sensitive
with those as well.

 

[Atlas]

1. Name AutoCorrect is off?

Details:
http://allenbrowne.com/bug-03.html

I've read your page. But in 2003 there's no such option in the
tools->options->general tab.... Multiple choices exist in the autocorrect
tab and autocorrect options.......

2. Corruption?
If this happens with this one particular database, but other databases are
okay, it may be a corruption. Suggestions:
http://allenbrowne.com/ser-47.html

Did this allready many times. No result. (BTW - A funny beheaviour:
Compacting the project shrinks it to 2.3MB; Importing everything, down to
1MB . ....... Huh??? What's that extra uncompacted 1.3 MB???)

3. Why the requery?

Why not? Records in the subform are not resorted automatically upon insert
(nice eh?) so users must requery to have a sorted subform.....

If #1 and #2 do not solve the problem, examine why the need for the F9.
What's changed? Is there any possiblity that the names in
LinkMasterFields/LinkChildFields could be misunderstood (e.g. if you used a
name such as Name, Date, or Section)?

Linkchild and linkmaster are set to an int(4) field (ID)

 

[Allen Browne]

I've read your page. But in 2003 there's no such option in the
tools->options->general tab.... Multiple choices exist in the autocorrect
tab and autocorrect options.......

There are indeed multiple check boxes.
Just turn them all off.

 

[Atlas]

Allen thanks for your help, but nothing to do, it keeps crashing. I flooding
MS with crash reports, hopeing the developers take a look at the dump and
try to find out why it crashes. After all the offending DLL's and the
offending application are their own, so if they have time, they should be
able to track down the error.......