Copy a split database (front end-back end)

Fire District has database of running cards (directions to streets). The
database has a front end and back end. We are building a firehouse in a
different location and I need to make another database for the new running
cards. I made a copy of the first database and pasted to another location,
but the new database tables are linked to the first database and the changes
would take place in both places.

How do I make a copy of the database and not have it linked to the first
database?

Thanks.

You need to re-link the tables with the Linked Table Manager. Tools
Database Utilities Linked Table Manager.

--
--Roger Carlson
MS Access MVP
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/...UBED1=ACCESS-L


"plfiredis" wrote in message
...
Fire District has database of running cards (directions to streets). The
database has a front end and back end. We are building a firehouse in a
different location and I need to make another database for the new running
cards. I made a copy of the first database and pasted to another
location,
but the new database tables are linked to the first database and the
changes
would take place in both places.

How do I make a copy of the database and not have it linked to the first
database?

Thanks.

It looks like the copied database is linked to the original database. I want
them to be seperate. How do I do that?

"Roger Carlson" wrote:

You need to re-link the tables with the Linked Table Manager. Tools
Database Utilities Linked Table Manager.

--
--Roger Carlson
MS Access MVP
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/...UBED1=ACCESS-L


"plfiredis" wrote in message
...
Fire District has database of running cards (directions to streets). The
database has a front end and back end. We are building a firehouse in a
different location and I need to make another database for the new running
cards. I made a copy of the first database and pasted to another
location,
but the new database tables are linked to the first database and the
changes
would take place in both places.

How do I make a copy of the database and not have it linked to the first
database?

Thanks.

Let's back up. You've got a split database (a front-end and a back-end). I
assumed you copied both to a new location. Is that true or did you just
copy the front end?

When you copy a front-end, it will still link to the original back-end. In
order to have it link to the new back-end, you need to use the Linked Table
Manager or delete the existing linked tables and link in the new ones.

--
--Roger Carlson
MS Access MVP
www.rogersaccesslibrary.com



"plfiredis" wrote in message
...
It looks like the copied database is linked to the original database. I
want
them to be seperate. How do I do that?

"Roger Carlson" wrote:

You need to re-link the tables with the Linked Table Manager. Tools
Database Utilities Linked Table Manager.

--
--Roger Carlson
MS Access MVP
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/...UBED1=ACCESS-L


"plfiredis" wrote in message
...
Fire District has database of running cards (directions to streets).
The
database has a front end and back end. We are building a firehouse in
a
different location and I need to make another database for the new
running
cards. I made a copy of the first database and pasted to another
location,
but the new database tables are linked to the first database and the
changes
would take place in both places.

How do I make a copy of the database and not have it linked to the
first
database?

Thanks.

plfiredis wrote:

Fire District has database of running cards (directions to streets). The
database has a front end and back end. We are building a firehouse in a
different location and I need to make another database for the new running
cards. I made a copy of the first database and pasted to another location,
but the new database tables are linked to the first database and the changes
would take place in both places.

It's going to be a bit of a pain dealing with two databases.

Why not put a field in key tables and forms telling you what FireHouse
you are dealing with? And use one database for both Firehouses.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

We actually have 3 firehouses right now and I have them all in the same
database. We are building 2 new firehouses that will replace 2 of our
current ones. They are in new locations, so I need to keep the current
directions (one database), and make a new set of directions for when we move,
so I would like that to be in a second database. After we move, I won't use
the first database.

Thanks.

"Tony Toews [MVP]" wrote:

plfiredis wrote:

Fire District has database of running cards (directions to streets). The
database has a front end and back end. We are building a firehouse in a
different location and I need to make another database for the new running
cards. I made a copy of the first database and pasted to another location,
but the new database tables are linked to the first database and the changes
would take place in both places.

It's going to be a bit of a pain dealing with two databases.

Why not put a field in key tables and forms telling you what FireHouse
you are dealing with? And use one database for both Firehouses.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

I copied the front and back end, but the front end tables show being linked
to the first table.

"Roger Carlson" wrote:

Let's back up. You've got a split database (a front-end and a back-end). I
assumed you copied both to a new location. Is that true or did you just
copy the front end?

When you copy a front-end, it will still link to the original back-end. In
order to have it link to the new back-end, you need to use the Linked Table
Manager or delete the existing linked tables and link in the new ones.

--
--Roger Carlson
MS Access MVP
www.rogersaccesslibrary.com



"plfiredis" wrote in message
...
It looks like the copied database is linked to the original database. I
want
them to be seperate. How do I do that?

"Roger Carlson" wrote:

You need to re-link the tables with the Linked Table Manager. Tools
Database Utilities Linked Table Manager.

--
--Roger Carlson
MS Access MVP
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/...UBED1=ACCESS-L


"plfiredis" wrote in message
...
Fire District has database of running cards (directions to streets).
The
database has a front end and back end. We are building a firehouse in
a
different location and I need to make another database for the new
running
cards. I made a copy of the first database and pasted to another
location,
but the new database tables are linked to the first database and the
changes
would take place in both places.

How do I make a copy of the database and not have it linked to the
first
database?

Thanks.

plfiredis wrote:

We actually have 3 firehouses right now and I have them all in the same
database. We are building 2 new firehouses that will replace 2 of our
current ones. They are in new locations, so I need to keep the current
directions (one database), and make a new set of directions for when we move,
so I would like that to be in a second database. After we move, I won't use
the first database.

Fair enough.

BTW I'm working on Granite Fleet Manager http://www.granitefleet.com/
which is quite useful now and will have a lot of features for fire
trucks and ambulances in the near future.

Tony.
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

All right. I repeat. You have to use the Linked Table Manager to re-link
the tables to those in the new back-end database.

--
--Roger Carlson
MS Access MVP
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/...UBED1=ACCESS-L


"plfiredis" wrote in message
news
I copied the front and back end, but the front end tables show being linked
to the first table.

"Roger Carlson" wrote:

Let's back up. You've got a split database (a front-end and a back-end).
I
assumed you copied both to a new location. Is that true or did you just
copy the front end?

When you copy a front-end, it will still link to the original back-end.
In
order to have it link to the new back-end, you need to use the Linked
Table
Manager or delete the existing linked tables and link in the new ones.

--
--Roger Carlson
MS Access MVP
www.rogersaccesslibrary.com



"plfiredis" wrote in message
...
It looks like the copied database is linked to the original database.
I
want
them to be seperate. How do I do that?

"Roger Carlson" wrote:

You need to re-link the tables with the Linked Table Manager. Tools
Database Utilities Linked Table Manager.

--
--Roger Carlson
MS Access MVP
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/...UBED1=ACCESS-L


"plfiredis" wrote in message
...
Fire District has database of running cards (directions to streets).
The
database has a front end and back end. We are building a firehouse
in
a
different location and I need to make another database for the new
running
cards. I made a copy of the first database and pasted to another
location,
but the new database tables are linked to the first database and the
changes
would take place in both places.

How do I make a copy of the database and not have it linked to the
first
database?

Thanks.

The linked table manager just shows the tables linked to the original
database backend and the choices are to select the tables to update the
linked tables. It doesn't give you the option to delete the link or change
it to new tables/database.

"Roger Carlson" wrote:

All right. I repeat. You have to use the Linked Table Manager to re-link
the tables to those in the new back-end database.

--
--Roger Carlson
MS Access MVP
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/...UBED1=ACCESS-L


"plfiredis" wrote in message
news
I copied the front and back end, but the front end tables show being linked
to the first table.

"Roger Carlson" wrote:

Let's back up. You've got a split database (a front-end and a back-end).
I
assumed you copied both to a new location. Is that true or did you just
copy the front end?

When you copy a front-end, it will still link to the original back-end.
In
order to have it link to the new back-end, you need to use the Linked
Table
Manager or delete the existing linked tables and link in the new ones.

--
--Roger Carlson
MS Access MVP
www.rogersaccesslibrary.com



"plfiredis" wrote in message
...
It looks like the copied database is linked to the original database.
I
want
them to be seperate. How do I do that?

"Roger Carlson" wrote:

You need to re-link the tables with the Linked Table Manager. Tools
Database Utilities Linked Table Manager.

--
--Roger Carlson
MS Access MVP
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/...UBED1=ACCESS-L


"plfiredis" wrote in message
...
Fire District has database of running cards (directions to streets).
The
database has a front end and back end. We are building a firehouse
in
a
different location and I need to make another database for the new
running
cards. I made a copy of the first database and pasted to another
location,
but the new database tables are linked to the first database and the
changes
would take place in both places.

How do I make a copy of the database and not have it linked to the
first
database?

Thanks.