Transferring DB without security

[Ramesh]

HI,

I have a database with user level security setup. I need to now transfer
the database to another system. Can I do this along with the same security
setup? Or can i do it without the security? any leads please?

Ramesh

 

[Tom Wickerath]

Hi Ramesh,

See the first download, "DBUtilities", available here:

http://www.accessmvp.com/SDaigle/index.htm


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

 

[Ramesh]

Thanks Tom for your response.

I checked out dbutilities. Seems like that one is useful to tranfer
permission from one database to another. What I need to do is to transfer
the data from one system to another. (with or without permissions)

Can this be done with the dbutilities?

Thanks again
Ramesh

 

[Tom Wickerath]

Hi Ramesh,

If you want to import the data into an unsecured Access application, I
*think* the following will work:

1.) Log into the secured database as a user who has permission to view the
data. Minimize this application, but keep it running.

2.) Create a new Access application. Import all tables that you wish to
de-secure.

Honestly, I do not use Access ULS, because it is really not all that secure.
So, if I've steered you wrong, and the above steps do not work, then I
suggest reposting to the Security newsgroup:

http://www.microsoft.com/office/com...spx?dg=microsoft.public.access.security&exp=1


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

 

[Ramesh]

Tom, I tried that .. i dont think its working. will try posting to the
security group as you suggested.

Thanks
Ramesh

 

[Rick Brandt]

Tom, I tried that .. i dont think its working. will try posting to the
security group as you suggested.

No it would not because any database file you create while in a secure workgroup
session will also be secured by that workgroup.

Now, if after importing all of the tables into the new file you granted full
permissions on the database object and all of the tables to the default "Users"
group then you would have a file that anyone else (using any workgroup file)
should be able to use.

 

[Tom Wickerath]

Hi Rick,

No it would not because any database file you create while in a secure workgroup
session will also be secured by that workgroup.

Correct me if I'm wrong, but wouldn't the above statement apply only if one
were permanently joined to a workgroup file other than the vanilla
system.mdw? In other words, the secured DB is opened using a shortcut that
includes the optional /wrkgrp switch with a full path to the .mdw file. The
second instance of Access, when opened to create a new database.....wouldn't
it be joined to System.mdw by default?


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

 

[Rick Brandt]

Hi Rick,


Correct me if I'm wrong, but wouldn't the above statement apply only if one
were permanently joined to a workgroup file other than the vanilla
system.mdw? In other words, the secured DB is opened using a shortcut that
includes the optional /wrkgrp switch with a full path to the .mdw file. The
second instance of Access, when opened to create a new database.....wouldn't
it be joined to System.mdw by default?

Yes, if you opened a second instance of Access then you would be back in
System.mdw, but then you wouldn't be able to import the tables from the secured
MDB (unless it was not secured properly).

 

[Tom Wickerath]

Hi Rick,

I tried the following tests using a newly created .mdb file (unsecured) with
a database that I believe to have been secured correctly (I did not create
this database). I first opened both databases: the new one by simply
double-clicking on it (joined to my vanilla System.mdw file) and the secured
one by opening it with a shortcut that includes the /wrkgrp switch with a
valid .mdw file.

You are correct...I was unable to import anything from the secured DB, when
using my new unsecured .mdb file. However, I had no trouble doing the
opposite: From within the secured file, I can freely export tables to my new
unsecured database.


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________