I have been experiencing an application error in one particular Access
application.

If I go into the application compile and save all modules then I can use the
application without the error occurring. However when I exit the application
and return I get the application will error again.
When I look the modules are somehow not compiled and sure enough compiling
them again solves the problem. Still I can not leave the application needing
the modules compiled every time it is used.

Upon further investigation I found the application performed fine on a
Windows 95 machine and that the application error only occurred under
Windows 2000. Also whilst the modules showed up as not being compiled on
when the application was opened on a Windows200 machine without doing
anything if I went to a win 95 machine it showed then as all being compiled.

I would have expected a Access application built on Windows 95 to work
equally well on Windows 2000. Is this just a freak occurrence or is there
some compatibility problem with the Microsoft platforms?

Normally I would give up on the application as corrupt and revert to a
backup but this one of those strange quirky occurrences that leaves you
wanting to know why.

Does anyone have any ideas please?

The actual error I get is:

MSACCESS.exe Application Error
The instruction art "0x651078f1" referenced memory at "0x0902ec4f". The
memory could not be read.
Click OK to terminate the program.