Replies

Well, Hans,

so my solution was too simple to be true…
I assume I indeed didn’t get these problems because no extra code was included for the close-button. Mea culpa.

Adn thanks again for giving your comments, also on this one – so at least no-one will use it without being warned about the consequences.

Hans

Thanks HansV,
there were still several pieces of valuable information in your reply which I didn’t know about…

I’ll try out the mde-solution and wait and see how far it’ll bring us. The rest, I’ll surely keep in mind.

((Meanwhile, I’ve built the file up again by (0) starting a new file (1) importing the actual tables from the corrupt one (compact) (2) importing the forms from an old backup which should be ‘clean’ enough (compact) (3) recreating the queries by copying (only) the SQL in design view from the original queries in the corrupt mdb (these couldn’t be opened in design view no more, but after importing them in another mdb, they did…) (compact) (4) splitting => backend+frontend (5) frontend => mde (6) copy mde => workstations. ))

ps just fyi…

About preventing a user to close a form by other means than the close-button…
I checked your post & it worked fine. Though, maybe also this variant, which I once used in one of my (few) app’s, is worth mentioning:
Private Sub Form_Close()
cmdClose_Click
End Sub
Advantage: you don’t need the variable & the user saves time: his first trial to ‘get out’ will work. And no matter how the form is closed, it’s closed as if the close button was used.
Disadvantage: I hope I didn’t overlook any possibilities…

Hey, Douglas,

So at least some of the mystery can be solved…
Thanks a lot about the hint about NOT designing while other user(s) is in the database. From this point of view, even for the smallest database, splitting it in front and back end ends up to be a good idea anyhow… And putting front ends on each work station, even with this tiny app, is, knowing this, worth a consideration as well.

Further, I’ll try to figure out if designing & developing the databases on my pc hard disk ( network) might enhance stability.

Right now, I wonder if there is an alternative to the worst case scenario: recovering an old old backup from before we started using it with more than one person, import the data from the latest version and restore the (fortunately – hopefully – limited) design changes made since then. Any suggestions?

Thanks a lot for the advice, and (?) the shared experience of Access 97 going ‘wobbly’!

Hans

Mark,
thanks for your reply.

=> I don’t know Jetcomp but I’ll sure check it out (enough search engines to show me the way).
=> The database wasn’t split (yet), as I thought it wouldn’t be necessary with its small complexity & amount of users (1 to occasionally 5). In case you’ld propose it as a solution: as I now even started getting problems with linked tables, I’m not sure it will help, but I’ll try it out…
=> More in my answer to Douglas Martin…