J
John Hardin
We have been running a particular Access application since version 97 -
upgrading the database with each new version of Access. Application ran fine
with Windows XP SP1, but began failing when we upgraded to SP2.
The switchboard form opens fine, but when we attempt to open another form
from the switchboard, we get "Microsoft Access has encountered a problem and
needs to close"
AppName: msaccess.exe AppVer: 10.0.2627.1 ModName: msjtes40.dll
ModVer: 4.0.8618.0 Offset: 0000413c
The form actually does display with data before the error appears. The
funny thing is that when I step through the code that displays the form in
debug mode, I don't get the error. However, as soon as I remove my
breakpoints and let the code run at full speed, I do get the error.
I have no trouble opening individual tables, running queries, or creating
reports. This application uses linked tables - some residing in another .mdb
and others in SQL Server. I was able to successfully refresh all table links.
Removing Windows XP SP2 from the machine solves this problem - but this is
NOT a viable long-term solution.
Has anyone else experienced a similar problem under SP2? Is there a
long-term fix? Thanks.
upgrading the database with each new version of Access. Application ran fine
with Windows XP SP1, but began failing when we upgraded to SP2.
The switchboard form opens fine, but when we attempt to open another form
from the switchboard, we get "Microsoft Access has encountered a problem and
needs to close"
AppName: msaccess.exe AppVer: 10.0.2627.1 ModName: msjtes40.dll
ModVer: 4.0.8618.0 Offset: 0000413c
The form actually does display with data before the error appears. The
funny thing is that when I step through the code that displays the form in
debug mode, I don't get the error. However, as soon as I remove my
breakpoints and let the code run at full speed, I do get the error.
I have no trouble opening individual tables, running queries, or creating
reports. This application uses linked tables - some residing in another .mdb
and others in SQL Server. I was able to successfully refresh all table links.
Removing Windows XP SP2 from the machine solves this problem - but this is
NOT a viable long-term solution.
Has anyone else experienced a similar problem under SP2? Is there a
long-term fix? Thanks.