Front-End MDE file crashes - no known cause?!?

[Larry Kahm]

Small shop, about 50 users, with distributed front-end MDE files pointing to
a back-end MDB on a server.

One particular desktop experiences crashes - on a seemingly irregluar basis.
No one else has reported such errors.

Event ID 1000: Fautling application msaccess.exe, version 9.0.0.6620,
faulting module msaccess.exe, version 9.0.0.6620, fault address 0x0004567a

Searching resuled in no hits.

But, just looking at one chunk of code that's often used during the crash, I
found the previous developer was changing the form's searchbox column widths
and bound column. Now I know that in an MDE you can't get at the designer
mode of a form, but can trying to set these properties be causing a problem?

Thanks!

Larry

 

[Rick Brandt]

Small shop, about 50 users, with distributed front-end MDE files
pointing to a back-end MDB on a server.

One particular desktop experiences crashes - on a seemingly irregluar
basis. No one else has reported such errors.

Event ID 1000: Fautling application msaccess.exe, version 9.0.0.6620,
faulting module msaccess.exe, version 9.0.0.6620, fault address
0x0004567a
Searching resuled in no hits.

But, just looking at one chunk of code that's often used during the
crash, I found the previous developer was changing the form's
searchbox column widths and bound column. Now I know that in an MDE
you can't get at the designer mode of a form, but can trying to set
these properties be causing a problem?
Thanks!

Larry

No. You can change most properties in an MDE, they are just not changed
permanently. THAT would require design view which is not available in an
MDE.

That user might have a corrupted install of Access, Office in general, with
Windows, or might have a missing or different library than one being
referenced by your file.