Is this the same as Inconsistent State Error?

Sticking my nose in here Debra.  
In my opinion you are just asking for trouble(s) by not having your db split. No matter how large or small if you have two or more people in the db, even if just occasionally, they need their own front end. On their computer.
You don't have to have big fancy networks or anything.  Just a shared folder where the back end is works just fine.
There are just too many issues than can corrupt your data if more than one person is using the db at a time.

Bare minimum make absolutely sure you are making GREAT back ups.

Alex - yes I am still occasionally getting the inconsistent error, but that is not the error I was talking about.  Its more of a warning that the user does not have exclusive access to the database.  They click through it and it goes away- there is no data loss.

Scott - I have thought about trying to split the database. To be honest I am scared to try it.  I am very much a self-taught novice and am concerned that I have already bit off more than I can chew... splitting may be the best thing for it, or it could make things way worse if I screw it up.

Back to my main question though -  is there a way to have the logon/logon occur only when the db opens and closes, as opposed to when the main menu form opens and closes? Because the db opens up onto the main menu, and it is a jumping off point for other items in the db, having it record the timestamp every time someone goes from the activities menu to the reports menu, via the main menu, seems redundant.  I just need to know who is in the database when they initially login, who has left the database, and if its locked up-- who is stuck in it, so I can be able to contact them and have them close out fully from access. It's always 'not me' in the database holding things up when I need to get in there and repair it after a crash.

I just added everything to my database and it works great EXCEPT if a user closes the database or exits on any other page it does not trigger the logOFF event.  I cannot see putting it on every page- because then things are going to get very messy. Any suggestions?  I have instructed the users to log out using the "Exit Database" icon on the main menu, but I cannot force them to do so.

Scott - I just tried to split my database and it crashed while it was creating the backend file and I got stuck :o(  Good thing I backed up.  I think I will hold off and maybe try again tomorrow.  Not sure what locked it up.  We run everything through citrix, so maybe it was something in there....

Debra if you make a copy of your data base, put it in a different folder on your computer, that only you have access to, do you still have problems?

Just guessing here but I suspect that your db may have been corrupted or damaged by having the crashes with others using it.  I would start out in the copy buy doing a Compact and Repair.

-------------------
Edit:  I just re-read your posts.  This comment, "We run everything through citrix, so maybe it was something in there...." worries me.
Are you in different locations?  Not on a network?

Citrix is a cloud based solution.  99.9% sure that is the issue.  Maybe Richard, Alex, or one of the others can confirm.

Originally it was just in the shared folder over the network that we access via our regular desktops, but it was ridiculously slow- and that was when it new.  So, we decided to try accessing the same folder through citrix and it cleared up the speed issue immediately.

I compact the db every night before I back it up. Not sure if that is ok to do...but that is what I usually do- especially if I make any changes to any objects.

I will attempt to split the db later today- will let you know if I encounter the same issue.  I think what happened last night had nothing to do with the db, but other changes made it Citrix by IT while I was working in there late last night.

Citrix is a remote desktop solution kind of like Access Database Cloud. But a Citrix server is also often used to host applications in house instead of just over the web. While it is certainly possible to run Microsoft Access over Citrix I cannot help you or support it because I personally have zero experience with Citrix. Here's an article that may help you: MS Access ' Deploying an Access Database using CITRIX

It runs very well actually.  The database in not in the cloud. It is in a shared folder on a regular server.  If we all try and access it via our regular VPN it is very slow with us in there. However, if we access the same folder, but through citrix, it is very quick.  I have no issues with citrix.  We have had no crashes today either (fingers crossed).  I will be splitting the database this evening.  Back to my original question though- is there any way to attach the logON/LogOFF event to the exiting of the database, rather than the closing of the main menu or another form? Thank you!

Nope. Has to be in the Close/Unload event of a Form. Just disable any way for the user to close the Main Menu unless they close the app.