Access XP Crashes on me.refresh

[LeighW]

I have developed an Access 2000 datbase, I have recently converted it to an Access 2002 datbase, which runs on a Windows XP workstation. The datbase has a frontend and backend (the backend is on a Windows 2000 server)

I have a form with 2 subforms on, within one of my modules I have used the me.refresh statement. This works fine until I enter data into the subforms - then I get the message:

Microsoft Access has encountered a problem and needs to close. We are sorry for the inconvenience.

When I click for more information I get:

AppName: msaccess.exe AppVer: 10.0.2627.1 ModName: msjtes40.dll
ModVer: 4.0.7328.0 Offset: 00007a15

As a test I have created a new command button with just me.refresh in its onclick event, and I still get the error - but only once data has been entered into the subform.

I have tried running regsvr32.exe for msjtes40.dll this is successful, I have visited the windows updates website and downloaded all the newest updates & patches.

Any help or pointers will be greatly recieved

Thanks in anticipation

Leigh Walker
Access Developer

 

[KenReay]

Hi

Have you tried repair and compact on both mdb's ?

If that dioes not improve situation, create new mdbs and import all objects from originals, relink tables and try again

Good Luck !

Regards

Ken Reay
Freelance Solutions Developer
Boldon Information Systems Ltd
Website needs upgrading, but for now -

http://www.kenneth.reay.btinternet.co.uk

UK

 

[ISisyphus]

Hi Leigh,

I have experienced almost the exact same thing. I have a db that was upgraded from an Access97 db. On the main form I have 2 subforms on a tab control. When changes are made to the records in the subforms I need to refresh the main - parent - form. I had this working until recently by using a form.parent.refresh in the after_update event of the subform. Now, every time a user makes a change on the subform they get the same error you describe only the version and modver numbers are different.

I've already tried everything Ken suggests to no avail so don't waste your time. I've had to use the requery method instead. Of course that isn't a good solution since the pointer is moved to the first record in the set after the requery is performed. I'm still interested in resolving the refresh issue but am now actively trying to figure out how to return the pointer to the record on the parent form to the one it was on when the requery method was called.

One other path I've considered is to remove the changes I've recently made at the request of the users and see if I can identify which one is causing the error to occur. Of course, this will be time consuming to say the least and time is something I do not have a lot of right now. At leaset now I know I'm not the only one experiencing this problem. I only wish I had a solution for you!

Good luck!

Sis