'Invalid bookmark' or 'database engine stopped the process' errorswithout corruption?

[Owen Jenkins]

I have a database running in Access (FE in 2000-2002 on local drive, BE
in 2000 on network server). It has a main form with several subforms and
several user-operated filtering options. Intermittently the users get an
'Invalid bookmark' error or the message "The Microsoft Jet database
engine stopped the process because you and another user are attemping to
change the data at the same time". This will also happen when a single
user operates the system entirely on the local PC, so it is not related
to multiple users or instances. And I don't specifically use bookmarks
anywhere in the code.

I have searched this newsgroup and the answers suggest either a
corrupted db or a conflict with the same data being edited
simultaneously in a form and a recordset etc. The db is not corrupted (I
have searched for erroneous data, have compacted, created a new db etc).
I have made sure the various subforms are refreshed between edits, and
have forced saving the record before entering subforms etc.

The problem is intermittent. I was able to fix a couple of issues which
were reproducible, but the errors now appear less frequently and less
predictably.

Can anyone give me any further suggestions?

Owen Jenkins

[BillCo]

Have you made sure that any recordsets used in code are closed and set
= nothing after use?

[Owen Jenkins]

BillCo wrote:

Have you made sure that any recordsets used in code are closed and set
= nothing after use?

Yep. Always do that. But thanks for the tip.

OJ

[David W. Fenton]

Owen Jenkins <[e-mail]> wrote in
news:43***********************@news.optusnet.com.a u:

I have searched this newsgroup and the answers suggest either a
corrupted db or a conflict with the same data being edited
simultaneously in a form and a recordset etc. The db is not
corrupted (I have searched for erroneous data, have compacted,
created a new db etc). I have made sure the various subforms are
refreshed between edits, and have forced saving the record before
entering subforms etc.

Have you really recreated the database and re-imported the data?

I'm not sure if it's the back end or the front end that's producing
the error, though.

Importing into a new MDB will carry over certain kinds of
corruption.

I'd also check that you have at least Jet 4.0 SP 6 or SP 8 (not SP
7, or anything at all before 6), and that you have at least SR 1 of
Access 2000.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[Owen Jenkins]

David W. Fenton wrote:

Owen Jenkins <[e-mail]> wrote in
news:43***********************@news.optusnet.com. au:

I have searched this newsgroup and the answers suggest either a
corrupted db or a conflict with the same data being edited
simultaneously in a form and a recordset etc. The db is not
corrupted (I have searched for erroneous data, have compacted,
created a new db etc). I have made sure the various subforms are
refreshed between edits, and have forced saving the record before
entering subforms etc.

Have you really recreated the database and re-imported the data?

I'm not sure if it's the back end or the front end that's producing
the error, though.

Importing into a new MDB will carry over certain kinds of
corruption.

I'd also check that you have at least Jet 4.0 SP 6 or SP 8 (not SP
7, or anything at all before 6), and that you have at least SR 1 of
Access 2000.

I've recreated the back end and re-imported the data, but haven't done
this with the front end. Maybe I'll try that since I suspect the problem
is the front end. (I also suspect it's a subform/recordset data conflict
that I haven't identified yet.)

Yes, all have Jet 4 SP 8 and Access 2002.

Another odd thing is that when the 'database engine has stopped the
process' error appears, if you don't do anything at all, not even click
OK on the error message, the same error pops up multiple times over the
top of the previous message, about once every 30 sec. And there is no
timer function anywhere in the db.

Owen

[johnnywags]

i'm facing similar situation. so intemitent that i tend to ignore it.
hoping it will go away. users are not happy with that stance. if you
solve it, please post your solution