Split databases: copies

[PeterJC]

I have a split database (Access 2007) with the back end on a server and
copies of the front end on various local hard drives. I want to make some
functional changes on the front end, and to test those changes with various
data entries etc.

I’ve copied and renamed the front and back ends of this application and have
linked the front end copy to the back end copy, but I find that when I make
data entries to the copied databases, the changes find their way into the
original back end file. It appears that the tables in the copied back end are
referenced in some way to the original back end, since a table ‘tabnm’ in the
original will be present in the opened copied front end together with another
table called ‘tabnm1’, and only the latter table will be linked to the copied
back end.

What do I do about this? I wondered if I should delink the copied front end
from the original back end before linking it t o the copied back end, but I
don’t know how to delink it.

Suggestions would be very welcome, thanks

 

[John W. Vinson]

I have a split database (Access 2007) with the back end on a server and
copies of the front end on various local hard drives. I want to make some
functional changes on the front end, and to test those changes with various
data entries etc.

I’ve copied and renamed the front and back ends of this application and have
linked the front end copy to the back end copy, but I find that when I make
data entries to the copied databases, the changes find their way into the
original back end file. It appears that the tables in the copied back end are
referenced in some way to the original back end, since a table ‘tabnm’ in the
original will be present in the opened copied front end together with another
table called ‘tabnm1’, and only the latter table will be linked to the copied
back end.

What do I do about this? I wondered if I should delink the copied front end
from the original back end before linking it t o the copied back end, but I
don’t know how to delink it.

Suggestions would be very welcome, thanks

All of the frontends have links to the original backend. Making a copy of the
backend doesn't change that in any way; and copies of the frontend will all
have the same links, again to the original backend.

If you want to create links to a different copy of the backend (say for
testing purposes, where you don't want to mess up the production data), you
need to make a copy of the backend and then open the "test" copy of the
frontend, and use (for A2003, not certain where this would be in 2007)
Tools... Database Utilities... Linked Table Manager. Select all the tables
that you want to relink (typically all of them), check the "Always prompt for
new location", and click OK. Navigate to the copy of the backend.

You'll need to relink to the production backend when you're satisfied with the
new version and want to distribute it to your users.

 

[golfinray]

I would suggest that you always have a "working" or "trial copy of the
database that you can play with and test on. Maybe because it is on the same
server it is linking somehow. Try moving your copy to some other drive.

 

[Tony Toews [MVP]]

I’ve copied and renamed the front and back ends of this application and have
linked the front end copy to the back end copy, but I find that when I make
data entries to the copied databases, the changes find their way into the
original back end file. It appears that the tables in the copied back end are
referenced in some way to the original back end, since a table ‘tabnm’ in the
original will be present in the opened copied front end together with another
table called ‘tabnm1’, and only the latter table will be linked to the copied
back end.

You've already received two good answers. But just to help see how
things are working hover your mouse over the linked table name. After
a second or so you should see a tool tip displayed which has the
location and name of the backend MDB.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a free, convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
Granite Fleet Manager http://www.granitefleet.com/

 

[Frank H]

If you did deleted the tables in your copied front end, and create new links
to the copied back end, and these tabnm tables are showing up without your
doing anything, then there is probably VBA code that is creating the tables
and links, probably for use as temp tables. Try looking through your VBA
modules, and then post that code back here. If it's code, somebody will jump
on it.