George,
No offense taken. You guessed it eactly right, I am just starting out with
Access and finding all sorts of mine fields.
The database that I am working on is only a single user and simply needs to
be transferred from one machine to another so I don't think I should have
problems with other user access.
Thanks for the help.
Regards
DJK
"George Nicholson" wrote:
> If you have a frontend/backend setup then the data is on a shared drive
> somewhere and *other people are using it*.
>
> If you do manage to "copy" the backend to another location and connect your
> frontend to it, it will be a stand-alone copy, no longer shared by others.
> Any changes you make to that data will *not* be seen by others. Likewise,
> any changes others make to the shared db will no longer be seen by you. Is
> that what you want?
>
> There are ways around that (replication, for one), but frankly, considering
> the level of question you are asking they are way above your current ability
> to implement (no offense intended, just you really, really, really don't
> want to go there).
>
> If you want to stay connected to the shared backend then you can 1) use the
> Linked table manager to identify the current backend location 2) copy your
> Frontend and 3) use the Linked table manager from your copied frontend to
> reconnect to the backend. The difference may just be a matter of drive
> mapping on the 2 machines: (for example: one machine maps the shared server
> to S:\ the other to U:\)
>
> Note: copying the backend while others actually have the file open could
> badly corrupt the file and its contents.
>
> --
> HTH,
> George
>
>
> "DJK" <(E-Mail Removed)> wrote in message
> news:EC4FC23D-E3A7-469A-99B2-(E-Mail Removed)...
> > Jeff,
> > Thanks for the help. Is there any easy way to identify the FE and BE on my
> > computer and what type of files should I be looking for?
> > Regards
> >
> > David
> >
> > "Jeff Boyce" wrote:
> >
> >> That would seem to suggest that your application is separated into a
> >> "front-end" (holds forms, reports, queries, ...) and a "back-end" (holds
> >> only the tables/data).
> >>
> >> If you copy a "front-end" (to CD or Flash or ...), you are NOT copying
> >> the
> >> back-end.
> >>
> >> To successfully copy an application from one PC to another on the same
> >> LAN,
> >> you would ONLY need to copy the front-end.
> >>
> >> To copy from one PC to another (disconnected) PC, you have to copy both
> >> front- and back-ends, AND you may need to re-link to the back-end tables
> >> (if
> >> the new home is not identical to the old...).
> >>
> >> Regards
> >>
> >> Jeff Boyce
> >> Microsoft Office/Access MVP
> >>
> >> "DJK" <(E-Mail Removed)> wrote in message
> >> news:46EDD717-4B67-43A0-A0DD-(E-Mail Removed)...
> >> >I am trying to copy an existing Access Database from one computer to
> >> >another.
> >> > I have seen the issues regarding copying to a CD and can copy to a
> >> > Flash
> >> > Drive. What is the best way to copy the database, including the data?
> >> > When
> >> > I
> >> > have copied it previously, the data is not copied at the same time.
> >>
> >>
> >>
>
>
>
|