Well, my first question is, is the database properly split and does each user have their own front end connected to a shared back end? Because if everyone is just connecting to that shared folder and working on the same database, it will definitely cause that problem.

Another thing is that although you can use Access wirelessly, I don't recommend it because if it loses its network connectivity for any moment at all, it will disconnect from the database and you'll have to restart. I recommend using Access on a wired network only. You could code in some stuff in VBA to automatically reconnect if it drops, but it's a pain.

I've done some stuff like this before with Unbound forms where if the form can't connect to the table it will reload itself. But I'm suspecting it's the first issue'if everybody is using the same ACCDB file and it's not split, then that will cause this problem.

If the connection goes on and off, it affects all applications that require the connection.  So the more prudent thing to do is find ways to fix that connection.  Get better wi-fi coverage with better wireless routers, add more access points, or hire professionals to set up enterprise-level wi-fi solutions.  In my old job, I had my roving warehouse people use cellphone 3G/4G connection to use a web interface on their web browsers.

Richard, While the DB is not properly split, it might be useful to point out that it is rarely used by more that 2 people at a time. My top suspicion is that we are forced to use it wirelessly because desktops don't even exist at my work. That being said, it remains connected unless you do both of the following: A) move to a different wifi area, and B) let your laptop go into standby. If only one of those things happen, you'll still be fine. But if both happen, you're definitely going to get the #Name? problem. I need the hands on training so I will take your advice and start working on making it a properly split DB. As of right now, the main DB is in a folder on the shared drive and everyone has a shorcut on their desktop. That way if they do something dopey like delete it, they are only deleting the shorcut. But I'll go through and make sure I have everything done properly for a correctly split DB. Thanks!

Yeah, it should be split and everyone has their own copy of the front-end... not sharing the same ACCDB front-end file that's on the server. A unique copy of the front-end. I have multiple laptops in my office too, and I've seen first-hand what can happen if I accidentally forget I have a database open on PC1 and open it and do stuff on PC2. It corrupts the database sometimes with just me using it. Spotty WiFi coverage won't help either.