B
BillieGoat
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
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