#Error/Invalid Bookmark

[Alc]

I've found a few posts about this subject, on the forum, so I'm guessing that my database (or at least one table therein) has become corrupt.

I've tried the various suggestions I could find (compact and repair, import into a new Db, etc) and none have worked. I have, however, located a version of the database from the day before this error first occurred. I've checked the problematic table and it contains no 'Error#' lines.

The single table affected contains a lot of data and is pretty irreplaceable. I have daily backups, so no information will actually get lost, but if I can't add any new data to it (for fear of corruption) it won't be much use.

1) What causes this problem? I can't seem to find a definite answer to this one.
2) Is there one definite fix I can use to prevent the problem occurring again?

 

[RuralGuy]

See if this link sheds any light on the topic.

 

[Alc]

I've printed it out and shall study it intently.

Thanks for the response.

 

[Rabbie]

Some points from personal experience. Most of this is covered in the link that RG posted.

1. Split your DB into FE/BE
2. Close your db in an organised way before you switch off your computer.
3. Compact and repair at regular intervals.
4. Keep regular backups so if disaster does strike you don't loose too much work.

 

[Alc]

Thanks for the advice.

1. Done. First thing I changed when I took over looking after this app.
2. Done. The 'X' has been disabled, so the users have to use my 'Close' button. Ties in with point 4. Some occasionally use Task Manager, but I've made sure that they know a record is kept of every time a user does/doesn't log out correctly and they're getting so scared of being blamed for any corruptions that might occur that they're gradually stopping.
4. Done each time the user logs out after having made one or more changes. They complain about the time it takes, but I'd rather suffer the moans than lose the data.

3. Is only point I'll need to work on. Perhaps add a compact and repair bit to the back up that runs, on certain dates.

 

[RuralGuy]

If you open an invisible form first when you launch the application and leave it open then it can do a lot of housekeeping chores for you. If the user were to press the "X" (not disabled of course) then this invisible form is the last to close and you could stop the close or do some housekeeping before you let the application quit. Just my $0.02

 

[Alc]

If you open an invisible form first when you launch the application and leave it open then it can do a lot of housekeeping chores for you. If the user were to press the "X" (not disabled of course) then this invisible form is the last to close and you could stop the close or do some housekeeping before you let the application quit. Just my $0.02

I do a similar thing with the 'Close' button I added.
The first thing to happen when it's clicked, is that a form is opened. In the 'On Open' event, I've added all the back-up code, etc. and a close application command. The extra code only runs if the user has made a change to one or more tables, this avoids getting them annoyed if they just log in to runa report and don't alter the data at all.