Most people don't realize that Access databases are ALWAYS secured. Access installs with a default workgroup file named System.mdw. It registers this default in the Registry and Access assumes that this is the workgroup you want to join when you open what you think of as an "unsecured" Access db and joins you to that workgroup as the admin user giving you all rights to the db. That makes the security transparent.
Apparently, your user has recently used a "secured" db. When you use the workgroup administrator to specifically join a workgroup, Access replaces the default workgroup name in the Registry with the one you just joined. Therefore, until you specifically join a different workgroup, the last one you joined now remains as your default workgroup. To get back to what looks like "unsecured" mode, have your user specifically join System.mdw.
This isn't surefire since many people also make the mistake of modifying System.mdw especially when they are playing around with security to learn how it works. We get many posts here from people who have done this. So if rejoining System.mdw does not resolve the problem, you'll need to get a clean copy of System.mdw and copy it to the correct directory on her PC. Be very carefule with this since each version of Access uses the same name for this workgroup file but they are stored in different directories. Make sure you get a copy of the correct version and that you install it in the correct directory.
To avoid this problem in the future when working with "secured" databases, make a shortcut to open the db and use the workgroup parameter to pass along the workgroup name. This method of opening a secured db does NOT modify the Registry so it won't leave you with a different default workgroup.
