All records in table disappeared

[Isaac]

The loging form is not a menu. It is a login form. It opens the menu when the login is successful. But instead of closing,it hides itself so that certain User information is always available from anywhere in the application without doing additional I/O to get it it.

When I said 'menu', I probably should have said 'non-data' form, which is what I consider to be any form not dealing with the actual data that the db is meant to manage.

Pretty much (with maybe a rare exception?) - NO form in my db's, which isn't dealing with core data, is bound. Period. That's more what I meant since we can quibble about the meaning of 'menu'.

 

[Isaac]

I would think the good thing is that you found the cause, and nobody had deliberately trashed the data. Luckily it only happened to a relatively innocuous data set. Could the same process destroy volatile data by accident?

Exactly along similar lines as I was thinking when I said I don't mix and match the concepts of menus vs. data.
You're lucky the only thing that disappeared was config type of info and not core data.

 

[Babycat]

I silently checked my login-form. Somehow, it bounds to tbl_User accidentally, it could be my intention in the past. But textboxes dont bound to any field. Therefore, I dont have "delete all" record issue. But for safety, I have removed bounded table from the form.

 

[The_Doc_Man]

Since we had a formal domain with the U.S. Navy, and the group policy downloads that occurred at each user's laptop's startup locked down the user's ability to diddle with certain symbolic objects, we could trust the domain names, computer names, and usernames AND could trust that the user had logged in successfully. I'm not at all saying you should do this, but rather offering the idea that if you have a formal and relatively trustworthy domain setup, the user's domain login name is another tool in the tool box that you could use to identify users.