I am hoping that Rick Sprague will read this and assist me. I was in the process of attempting to apply some sort of security to a database that we have residing on Citrix. All users also get Access 97 from the same location. I created the workgroup file and a blank secure database locally, but used Access 97 from Citrix. Now... I have somehow applied security to ALL of the databases out there and can not remove it. I have no problems switching workgroup files back to the system.mdw from home, but when I attempt it here at work, I constantly am presented with the logon for Access. HELP!
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Major problem! Citrix and Workgroup file. All DB's now have security! 1
- Thread starter RAWC
- Start date
-
1
- #2
I don't know what Citrix is, so I'm not sure I'm prepared to help you. One thing I can tell you, though, is that when previously unsecured databases suddenly start asking for logons, it can only be because (1) the SYSTEM.MDW file being used is no longer the default one installed with Access, or (2) the user's registry settings specify a secure workgroup file as the default system database. The latter could happen either because the users have used the Workgroup Administrator to join a secure workgroup, or because their registry settings have somehow been changed. If Citrix has something to do with centralizing user registry settings or Access profiles on one server, maybe that would be causing it.
It could also be that your users are using the Access profile feature, or are using shortcuts that contain the /wrkgrp switch in the command line. Either of these could select a non-default workgroup file to be used as the system database.
The most likely possibility is that you've named your secured workgroup file SYSTEM.MDW and it has replaced the default Access system database. I would recommend that you never, ever name a secured workgroup file SYSTEM.MDW. You'll need to find a default SYSTEM.MDW (the original one installed with Access) and replace your secured workgroup file with it to restore users to normal. Then we can set about figuring out how Access on each user's system is identifying the system database to use, and thus how to create a secured one that won't collide with their everyday one.
Am I getting close? Rick Sprague
It could also be that your users are using the Access profile feature, or are using shortcuts that contain the /wrkgrp switch in the command line. Either of these could select a non-default workgroup file to be used as the system database.
The most likely possibility is that you've named your secured workgroup file SYSTEM.MDW and it has replaced the default Access system database. I would recommend that you never, ever name a secured workgroup file SYSTEM.MDW. You'll need to find a default SYSTEM.MDW (the original one installed with Access) and replace your secured workgroup file with it to restore users to normal. Then we can set about figuring out how Access on each user's system is identifying the system database to use, and thus how to create a secured one that won't collide with their everyday one.
Am I getting close? Rick Sprague
- Thread starter
- #3
Rick,
Citrix is used to "hold" applications on a server. Then users access them there rather than having them installed locally on their pc. I did not name the new workgroup system.mdw. And... I have tried replacing the copy of the system.mdw with one from my home version of Access 97. You may have hit the nail on the head with the the registry. I will try a few things and I do appreciate you getting back to me! Wish me luck.
Renae
Citrix is used to "hold" applications on a server. Then users access them there rather than having them installed locally on their pc. I did not name the new workgroup system.mdw. And... I have tried replacing the copy of the system.mdw with one from my home version of Access 97. You may have hit the nail on the head with the the registry. I will try a few things and I do appreciate you getting back to me! Wish me luck.
Renae
- Thread starter
- #4
Rick,
This is what had to be done... UGH!!
We had to restore the last good backup of the databases, the office products, and the registry (I also included restoring the backup of the system.mdw just in case). So you were right. Thank you so much for nudging me in the right direction!
Renae
This is what had to be done... UGH!!
We had to restore the last good backup of the databases, the office products, and the registry (I also included restoring the backup of the system.mdw just in case). So you were right. Thank you so much for nudging me in the right direction!
Renae
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question
- Locked
- Question
