G
Guest
I have a form with a couple of sub forms on it. On both the form and the
subforms, there is information about people which has been returned by the
form's and sub forms' queries.
I open a second form (without closing the first) which allows me to, among
other things, change information about those people, including potentially
correcting the spelling for their names.
When I am done on the second form, I close it. Since I might have changed
the spelling of a name, I want the first form and its sub forms to reflect
the new spellings, so I execute a Refresh.
This used to work in Access 2000 but in Access 2002, I get the dialog box
"Microsoft Access has encountered a problem and needs to close. We are sorry
for the inconvenience."
The write-up in the knowledge base about this talks about the error
occurring in Owc10.dll and about how infinite recursion is causing the
problem.
My error details say the problem is with msjtes40.dll. I cannot find any
info on this specific issue.
The write-up further talks about not doing a Refresh in certain event
handlers, but does not mention the one I am doing it in, which is an OnClick.
Does anyone have any knowledge about fixing this problem, or whether there
is a patch available to download?
Alternatively, any suggestions on which handlers I might use to accomplish
the refresh? I have tried OnActivate, which has the same bad result.
subforms, there is information about people which has been returned by the
form's and sub forms' queries.
I open a second form (without closing the first) which allows me to, among
other things, change information about those people, including potentially
correcting the spelling for their names.
When I am done on the second form, I close it. Since I might have changed
the spelling of a name, I want the first form and its sub forms to reflect
the new spellings, so I execute a Refresh.
This used to work in Access 2000 but in Access 2002, I get the dialog box
"Microsoft Access has encountered a problem and needs to close. We are sorry
for the inconvenience."
The write-up in the knowledge base about this talks about the error
occurring in Owc10.dll and about how infinite recursion is causing the
problem.
My error details say the problem is with msjtes40.dll. I cannot find any
info on this specific issue.
The write-up further talks about not doing a Refresh in certain event
handlers, but does not mention the one I am doing it in, which is an OnClick.
Does anyone have any knowledge about fixing this problem, or whether there
is a patch available to download?
Alternatively, any suggestions on which handlers I might use to accomplish
the refresh? I have tried OnActivate, which has the same bad result.