MS Access data conversion - Error Message The Microsoft Jet Engine stopped the process because

Author

Error Message The Microsoft Jet Engine stopped the process because

BillieGoat

2005-04-06, 8:05 pm

I have a client that has a database that we have converted from 97 to 2003.
We converted the programs first and things seemed to run fine except that it
was slow. We converted the data and we are now getting the Error Message:
"The Microsoft Jet Engine stopped the process because you and another user
are attempting to change the same data at the same time".
This error occurs on two different subforms of a parent form. One of the
subforms has some complex calculations the other does not and really doesn't
have any extra VB code behind it. The error only occurs occationally and
doesn't seem to have a ryhme or reason. It does not occur when I have my
tables link locally but occurs when I am connected to the "server" PC which
is a Windows XP Professional PC.
We can enter the same claim again and not get the error. It happens on all
the PCs that are using this database.
I have been working on this issue for several months and tried optimizing
everything I could. While this has spead up the database, we are still
getting the error.
I had the same problem at another client and optimized the database, found
that many of the problems were network related and the issue seems to have
gone away. I have done the same thing to this database but I am still getting
the error.

Help!!!!
Billie

Ken Snell [MVP]

2005-04-06, 8:05 pm

I have gotten this error when using a subform and running code in the
subform and the main form at the same time. It can be a timing issue for the
code. What happened for me is that the person was editing data in the
subform record, then clicked directly onto the main form onto a command
button that updated the data. Because of a short timing issue, the main form
tried to save the data while the subform was still "dirty" and hadn't saved
its data yet.

Here is info from a post I did back in September 2003:
----
This error can occur in many ways (see numerous KB articles about it), but
the first place to look is for situations where the user can begin editing a
record in a subform (makes it dirty), then clicks onto another part of the
form (another subform, or the main form) and causes some code to run on that
new area of the form. The initial subform is NOT written to its recordsource
at that time; the subform is still dirty. If your other code is trying to
edit the same record/table info, you can get this error.

I have overcome this problem on some forms by forcing the subform to save
its current record in the code that runs on the other part of the form.

It also can be a sign of corruption.

See this URL for some KB articles (watch for line-wrapping, as the URL is
one line):
http://support.microsoft.com/search...r /> Jet+databa
se+engine+stopped+th
e+process+because&KeywordType=PHRASE&maxResults=150&Titles=false&numDays=

----

Take a look at your setup and see if it's possible that this error is
resulting from such a conflict in your code. The fact that you see it on a
network but not on your local setup is symptomatic of this problem.

If this is the problem, you may need to reprogram the form so that the code
conflict doesn't occur (cannot click on a button to cause more code to run
until the one is done), to force the main form's code to finish the
subform's code by forcing it to save the record in the subform before the
main form continues, or to put a delay in the main form's code of a few
seconds or so to allow the subform to finish its updating.
--

Ken Snell
<MS ACCESS MVP>

"BillieGoat" < BillieGoat@discussio
ns.microsoft.com> wrote in message
news:E31C86BF-4AE3-477D-B478- 70BBF33C204A@microso
ft.com...
>I have a client that has a database that we have converted from 97 to 2003.
> We converted the programs first and things seemed to run fine except that
> it
> was slow. We converted the data and we are now getting the Error Message:
> "The Microsoft Jet Engine stopped the process because you and another user
> are attempting to change the same data at the same time".
> This error occurs on two different subforms of a parent form. One of the
> subforms has some complex calculations the other does not and really
> doesn't
> have any extra VB code behind it. The error only occurs occationally and
> doesn't seem to have a ryhme or reason. It does not occur when I have my
> tables link locally but occurs when I am connected to the "server" PC
> which
> is a Windows XP Professional PC.
> We can enter the same claim again and not get the error. It happens on all
> the PCs that are using this database.
> I have been working on this issue for several months and tried optimizing
> everything I could. While this has spead up the database, we are still
> getting the error.
> I had the same problem at another client and optimized the database, found
> that many of the problems were network related and the issue seems to have
> gone away. I have done the same thing to this database but I am still
> getting
> the error.
>
> Help!!!!
> Billie

Sponsored Links