(Msg. 1) Posted: Fri Oct 10, 2008 10:46 am
Post subject: Copy a split database (front end-back end) Archived from groups: microsoft>public>access>tablesdbdesign (more info?)
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?
(Msg. 2) Posted: Fri Oct 10, 2008 1:54 pm
Post subject: Re: Copy a split database (front end-back end) [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
You need to re-link the tables with the Linked Table Manager. Tools >
Database Utilities > Linked Table Manager.
"plfiredis" <plfiredis DeleteThis @discussions.microsoft.com> wrote in message
news:6782B6C5-42C8-4A78-9870-1E668EEF7F7F@microsoft.com...
> 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.
(Msg. 3) Posted: Fri Oct 10, 2008 1:54 pm
Post subject: Re: Copy a split database (front end-back end) [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
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/wa.exe?SUBED1=ACCESS-L >
>
> "plfiredis" <plfiredis.TakeThisOut@discussions.microsoft.com> wrote in message
> news:6782B6C5-42C8-4A78-9870-1E668EEF7F7F@microsoft.com...
> > 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.
>
>
>
(Msg. 4) Posted: Fri Oct 10, 2008 3:22 pm
Post subject: Re: Copy a split database (front end-back end) [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
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.
"plfiredis" <plfiredis RemoveThis @discussions.microsoft.com> wrote in message
news:573F151A-E2BF-40D5-A5C2-1CCF33CC4BD1@microsoft.com...
> 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/wa.exe?SUBED1=ACCESS-L >>
>>
>> "plfiredis" <plfiredis RemoveThis @discussions.microsoft.com> wrote in message
>> news:6782B6C5-42C8-4A78-9870-1E668EEF7F7F@microsoft.com...
>> > 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.
>>
>>
>>
(Msg. 5) Posted: Fri Oct 10, 2008 10:16 pm
Post subject: Re: Copy a split database (front end-back end) [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
>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/
(Msg. 6) Posted: Mon Oct 13, 2008 8:34 am
Post subject: Re: Copy a split database (front end-back end) [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
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 <plfiredis RemoveThis @discussions.microsoft.com> 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/ >
(Msg. 7) Posted: Mon Oct 13, 2008 8:40 am
Post subject: Re: Copy a split database (front end-back end) [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
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" <plfiredis.DeleteThis@discussions.microsoft.com> wrote in message
> news:573F151A-E2BF-40D5-A5C2-1CCF33CC4BD1@microsoft.com...
> > 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/wa.exe?SUBED1=ACCESS-L > >>
> >>
> >> "plfiredis" <plfiredis.DeleteThis@discussions.microsoft.com> wrote in message
> >> news:6782B6C5-42C8-4A78-9870-1E668EEF7F7F@microsoft.com...
> >> > 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.
> >>
> >>
> >>
>
>
>
(Msg. 8) Posted: Mon Oct 13, 2008 3:02 pm
Post subject: Re: Copy a split database (front end-back end) [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
>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 times are: Eastern Time (US & Canada) (change) Goto page 1, 2
Page 1 of 2
You can post new topics in this forum You can reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
Home
Forums
Home
FAQ
Profile
Private Messages
Log in
Office Other