ACCESS "Invalid bookmark" error

[dkaplan]

I am running an Access 2000 application in a network environment. In a few of the subforms users occasionally see an message which says: "Not a valid bookmark" when attempting to add a record. When this happens the fields in the add row all contain "#Error". When the form is closed, then reopened, all of the added data appears, as entered.

All forms in this db are set to record level locking.
The error occurs sporadically and, so far, has not been reproducible.

Has anyone had experience with this?
Dennis

 

[TheAceMan1]

How are ya dkaplan . . . . .

Post the code for adding a record!

Hard to tell unless we see this . . . . .

See Ya! . . . . . .

 

[dkaplan]

The main form, and all subforms are bound forms.
So there is no code.

I should probably also mention that the development is done in an Win 2000 environment, while many of the users are on NT.

(This has been the case for years, and never a problem.)

All have Access 2000.

Dennis

 

[seaport]

I had exactly the same problem. I think it is a database issue rather than a programming issue. This error apears when the user attempts to insert the first record in the subform.

Although there are vb code in the main form and subform in my Access 2000 database, no code is executed before this error appeared. As dkaplan pointed out, there was even no code in his database.

Other information about this problem:
1. It never occurs if both front-end and back-end database is on the same drive.
2. It starts happening when the back-end database is getting bigger. One of database started getting it when it reaches 120M, and the other one started getting it when it reaches 30M.

I tried compacted and repairing the database and even rebuilt the backend database (importing all tables into a blank Access 2000 database), but I still could not stop the error. It occurs randomly and there is no way to debug.

Seaport

 

[TheAceMan1]

dkaplan . . .

Is this a frontend/backend affair?

See Ya! . . . . . .

 

[dkaplan]

Yes.

The problem seems to have gone away once all of the users switched to newer XP computers.

Seaport - I have received this error with both front & back ends on the same network drive (but different directories)

It started immediately after adding a fairly complicated subform.

It also seemed to coincide with times when there was a slow network response. The network has since been upgraded and that might also help explain why it went away.

Anyway, subforms and slow network response seem to be the magic ingredients for this problem. One last think I can think of is trying to explicitly control the focus after the user has updated the subform. My users were seeing the error immediately after leaving the subform.

There were a coulpe of things I did with the focus but, I was never sure that that was really what stopped the problem.