Import Objects from a Secured Database (Windows XP Professional/Access XP

Topic

New Reply

I want to import all of the database objects from a secured split database into a combined single file. I can export each object individually, but there are so many it will take a couple of hours (or more) to do them one at a time. If I go the import direction I get a message that I don’t have permissions to import. I have admin permissions for the database object. I have also tried to select multiple objects for export, but don’t have the ability to make a multiple select in the database window. Is there an easy way to bring all of the database objects into a clean file? My ultimate goal is to be able to easily reference work I have done on this database without having to deal with all of the security and links.

Reply | Quote

Replies

This probably has something to do with the security file being used – by default it is named System.mdw – do you get a login prompt when you work from the split front-end? Also, do you get a login prompt when you open the database you are trying to import into. It may also have to do with the owner of the database – you can check that from the security permissions tab. If it says Unknown then somehow the ownership of the database has been lost. In any event, if you have full permissions for all objects on the Admin account, you should be able to import everything into a new database. Using the File/Get External Data/Import and specifying the appropriate database, you should be able to choose the Select All for each class of objects and then let it import. Hope this helps – if not please post back with more details.

Reply | Quote

Hi Wendel,

Thank you for the quick reply. Yes, I do get a login prompt when I open the front end database, I do not get a login prompt when I try to import from this database. I think this is the problem, I am not sure why I am not getting the prompt unless the new database contaner need to use the same security file? I want the clean database to not need the security file to be opened. The creator of the secured database is still an account, but I am not the creator of the database object and I don’t think anyone kept the password for the account for the creator. Any ideas or direction is appreciated.
Carla

Reply | Quote

Sorry to not respond sooner – I’m travelling (and fighting a cold) and haven’t had much web access.

That suggests that you are using a shortcut to start the secured database that contains a pointer to the security file. Either create a similar shortcut for the new database, or join that security file using the menu, and then see if you can import things. That isn’t guaranteed to let you in, but if your account that login with lets you read the tables directly, then you should be able to import things. In any event you should be able to import the objects in the front-end, but queries may have been set to run with owner permissions, in which case you may not be able to import the tables. Then you may need to copy the entire back-end database, give it a different name so you can test with it, and reconnect the tables in the front-end to that database.

If that doesn’t get you working, let us know.

Reply | Quote

Hi Again,

By joining the workgroup in the new database container I was able to import the all of the objects except the action queries, which is progress. I could export the queries individually, but this still leaves me with a secured copy. I have in the past gone through the process detailed in the Microsoft knowledge base to extract a database out of the security scenario without any success. The only way I have been able to accomplish this is by exporting each object one at a time. My hope is that ther is an easier way that I am not aware of. I have looked at the link one of the Access moderators provided for securing an Access database and it was a lot of great information, but not much on how to get a database out of the security.
Again thank you for your suggestion.
Carla

Reply | Quote

To really unsecure the database you will need to login as Admin when you create the new database, but while connected to the secured system.mdw. If you cannot remember the password, and cannot reset it, then the individual export is the only way I know of to unsecure it. Again sorry for the long delay in responding.

Reply | Quote

Hi Wendell,

Sorry it took me so long to get back, I have been out of the office for a couple of days

Thank you for confirming what I probably already knew about exporting objects one at a time. I was looking for an easier way. What I have decided to do is use a 2G USB drive and just take all the files for the 4 main databases to my home PC in their entirety. I have a Word document with all the target strings for the shortcuts for local C drive security file locations and network security file locations so I can just copy and paste them into the shortcuts when I change the physical locations of the databases. I created the Word document a few months ago so I could continue development work on my local PC if the network where the security files are stored went down easily. Not a very elegant solution, but it will be a reasonable solution.
Thank you for the suggestions and information.
Carla

Reply | Quote

Hi Wendell,

Sorry it took me so long to get back, I have been out of the office for a couple of days

Thank you for confirming what I probably already knew about exporting objects one at a time. I was looking for an easier way. What I have decided to do is use a 2G USB drive and just take all the files for the 4 main databases to my home PC in their entirety. I have a Word document with all the target strings for the shortcuts for local C drive security file locations and network security file locations so I can just copy and paste them into the shortcuts when I change the physical locations of the databases. I created the Word document a few months ago so I could continue development work on my local PC if the network where the security files are stored went down easily. Not a very elegant solution, but it will be a reasonable solution.
Thank you for the suggestions and information.
Carla

Reply | Quote

To really unsecure the database you will need to login as Admin when you create the new database, but while connected to the secured system.mdw. If you cannot remember the password, and cannot reset it, then the individual export is the only way I know of to unsecure it. Again sorry for the long delay in responding.

Reply | Quote

Hi Again,

By joining the workgroup in the new database container I was able to import the all of the objects except the action queries, which is progress. I could export the queries individually, but this still leaves me with a secured copy. I have in the past gone through the process detailed in the Microsoft knowledge base to extract a database out of the security scenario without any success. The only way I have been able to accomplish this is by exporting each object one at a time. My hope is that ther is an easier way that I am not aware of. I have looked at the link one of the Access moderators provided for securing an Access database and it was a lot of great information, but not much on how to get a database out of the security.
Again thank you for your suggestion.
Carla

Reply | Quote

Sorry to not respond sooner – I’m travelling (and fighting a cold) and haven’t had much web access.

That suggests that you are using a shortcut to start the secured database that contains a pointer to the security file. Either create a similar shortcut for the new database, or join that security file using the menu, and then see if you can import things. That isn’t guaranteed to let you in, but if your account that login with lets you read the tables directly, then you should be able to import things. In any event you should be able to import the objects in the front-end, but queries may have been set to run with owner permissions, in which case you may not be able to import the tables. Then you may need to copy the entire back-end database, give it a different name so you can test with it, and reconnect the tables in the front-end to that database.

If that doesn’t get you working, let us know.

Reply | Quote

Hi Wendel,

Thank you for the quick reply. Yes, I do get a login prompt when I open the front end database, I do not get a login prompt when I try to import from this database. I think this is the problem, I am not sure why I am not getting the prompt unless the new database contaner need to use the same security file? I want the clean database to not need the security file to be opened. The creator of the secured database is still an account, but I am not the creator of the database object and I don’t think anyone kept the password for the account for the creator. Any ideas or direction is appreciated.
Carla

Reply | Quote

This probably has something to do with the security file being used – by default it is named System.mdw – do you get a login prompt when you work from the split front-end? Also, do you get a login prompt when you open the database you are trying to import into. It may also have to do with the owner of the database – you can check that from the security permissions tab. If it says Unknown then somehow the ownership of the database has been lost. In any event, if you have full permissions for all objects on the Admin account, you should be able to import everything into a new database. Using the File/Get External Data/Import and specifying the appropriate database, you should be able to choose the Select All for each class of objects and then let it import. Hope this helps – if not please post back with more details.

Reply | Quote