Copying a split database

[louisa]

Hi all,

I have created a database which has been split the back end is on a server, and the front end has been sent to various users.

We now have another company and instead of creating a new database i thought i could simply copy the one already created and delete that data ready for the new data to go in. I have tried various ways of copying this but any amendments i do it changes my original database (i dont want this to happen)

Any ideas on how i can copy it without it affecting any of the existing data if removed?

Many thanks for your help.

 

[Guus2005]

You copied the backend to a new location and removed the data?
You copied the frontend to a new location?

Start the frontend with the shift key pressed to avoid the autoexec macro from being started.

Go the your database window and right click an atttached table, select Linked Table Manager. Select all and check "always prompt for a new location". Now select the new and emptied database backend.

Voila. HTH

 

[louisa]

Thank you for your help, that has worked perfectly, however now i am trying to rename the database and it spits out an error that it cannot find the back end but if i keep the old name is doesnt spit out that error. Any ideas?

 

[Guus2005]

Change the name of the backend. Then open the frontend (with shift) en relink the attached tables to the backend with the new name.

You shouldn't get any error messages.

HTH

 

[gemma-the-husky]

Ok

what happens is:

A linked table is show in an acces database window with a symbol - eg, a linked access table has an arrow, a linked SQL/ODBC table has a world symbol.

In setting up this link, access stores the path to the backend database for each link (so that you can in theory link each table to a different backend

So if the target of that path can no longer be found, because you renamed it in windows, then the link fails. Which is why you need to rebuild the link.

A lot of developers will have startup code in place to check and verify that the links can be found, because eg, a netwrok error would also cause them to fail.


the actual stored connection is a string, which can be read using the connect property of the tabledef object

msgbox currentdb.tabledefs("sometable").connect