R
rjweiss777
Greetings:
Here’s my dilemma. I have been asked by a company to perform what I
thought would be a simple task. The company has a small tcp/ip lan setup
and has two databases on the network. All of the computers, the network,
and the databases were set up by individuals from other companies, each
adding their own unique touch. These people are not around any longer.
Is there any way to take a database that currently uses a workgroup
information file called AEC.mdw which contains the security information
for the database and change it so that the database points back to the
generic System.mdw workgroup information file that all databases point
to initially when Access is originally loaded?
The database resides on a network server. The AEC.mdw workgroup
information file also resides on the network server in the same
directory. All of the machines that are running Microsoft Access have
joined the AEC.mdw workgroup that resides on the network server.
What the company has requested is that all of the machines point back to
the original System.mdw workgroup information file (so that no login or
security information is required for any current or new databases that
are created).
The catch is, if you set Access to point back to the System.mdw file
when you try to open the databases that have security information
relevant to the AEC.mdw file then you don’t have permission to even open
the database.
There are other development projects in the works and the users are
complaining about having to reset the environment to AEC.mdw then back
to the System every time they change databases. It’s confusing and
cumbersome.
I have read the Access Security FAQ and followed section 34 on how to
de-secure a database. I have followed (at least everything that it said
to do) and I still can’t disengage from the AEC.mdw file. I was able to
get rid of the passwords but when I tried to open the database with
access joined to the System.mdw file it said I didn’t have the
permissions to access the database.
Unless I can work around this I’m going to have to create a new database
(that is pointing to the vanilla System.mdw) then I’m going to have to
figure out a way to export or import all of the forms, tables, queries
and reset the relationships for about 65 or so tables.
Does anyone have any ideas?
I would really appreciate any help. I’m needing a fresh perspective.
--
Thanks,
RJ
Posted via http://dbforums.com
Here’s my dilemma. I have been asked by a company to perform what I
thought would be a simple task. The company has a small tcp/ip lan setup
and has two databases on the network. All of the computers, the network,
and the databases were set up by individuals from other companies, each
adding their own unique touch. These people are not around any longer.
Is there any way to take a database that currently uses a workgroup
information file called AEC.mdw which contains the security information
for the database and change it so that the database points back to the
generic System.mdw workgroup information file that all databases point
to initially when Access is originally loaded?
The database resides on a network server. The AEC.mdw workgroup
information file also resides on the network server in the same
directory. All of the machines that are running Microsoft Access have
joined the AEC.mdw workgroup that resides on the network server.
What the company has requested is that all of the machines point back to
the original System.mdw workgroup information file (so that no login or
security information is required for any current or new databases that
are created).
The catch is, if you set Access to point back to the System.mdw file
when you try to open the databases that have security information
relevant to the AEC.mdw file then you don’t have permission to even open
the database.
There are other development projects in the works and the users are
complaining about having to reset the environment to AEC.mdw then back
to the System every time they change databases. It’s confusing and
cumbersome.
I have read the Access Security FAQ and followed section 34 on how to
de-secure a database. I have followed (at least everything that it said
to do) and I still can’t disengage from the AEC.mdw file. I was able to
get rid of the passwords but when I tried to open the database with
access joined to the System.mdw file it said I didn’t have the
permissions to access the database.
Unless I can work around this I’m going to have to create a new database
(that is pointing to the vanilla System.mdw) then I’m going to have to
figure out a way to export or import all of the forms, tables, queries
and reset the relationships for about 65 or so tables.
Does anyone have any ideas?
I would really appreciate any help. I’m needing a fresh perspective.
--
Thanks,
RJ
Posted via http://dbforums.com