Removing Security

  • Thread starter Thread starter Mike
  • Start date Start date
M

Mike

I attempted to remove security by following the directions
from Help. Manage user & group account... Delete accounts
and remove users.

I created a new database and imported all the objects from
the old secured database into the new database. But when
I attempt to use the Security wizard on this new database,
I get a message saying that I cannot use this utility as
administrator. I should log in as another user or create
a new database and import the objects.

Why does the new database still think there is a workgroup
file associated with it? I can open it without the use of
a workgroup file.

Thanks
Mike
 
(snip)
Why does the new database still think there is a workgroup
file associated with it? I can open it without the use of
a workgroup file.
Click to expand...


Further to what Rick said.

When you double-click a database to open it, this is what *does not* happen:

- Windows starts Access;
- Access opens the database file;
- Access sees what workgroup file is associated with that database;
- Access opens that workgroup file.

*This* is what happens:

- Windows starts Access;
- Access decides what workgroup file to use - and it does this
without any consideration whatever, of which database file
you are trying to open. The database file is completely irrelevant
to the question of which workgroup file Access will open next.
- Access opens that workgroup file;
- THEN Access opens the database file.

In other words, the workgroup file is a "per Access session" thing - not a
"per database" thing.

HTH,
TC
 
The user's database is stored locally on her harddrive in error. When I
moved it to the network drive, I cant get the workground file to find the
secure database. I thought I could create a new database on the network
drive, then import all the objects into it. Then create a new workgroup
file pointing to that database. Then copy the shortcut and put it on the
other users desktops.
 
Mike said:
The user's database is stored locally on her harddrive in error. When I
moved it to the network drive, I cant get the workground file to find the
secure database. I thought I could create a new database on the network
drive, then import all the objects into it. Then create a new workgroup
file pointing to that database. Then copy the shortcut and put it on the
other users desktops.
Click to expand...

Read TC's response. Workgroup files do not "find" database files. Moving your
database should have zero impact on how the security/workgroup aspect of Access
functions. The one exception I can think of is if you are using a custom shortcut to
launch a file that contains a command line parameter for selecting a non-default
workgroup, then obviously the shortcut "cares" where the database file is and would
have to be changed if the file were moved. As long as the workgroup file's location
stayed the same though it would not impact how the mdw file was loaded at startup.
 
Back
Top