I copied a database both front end and a back end from a network folder to a
user's c drive for use on his laptop. I re linked the front end and
backend.Later on, I tried to copy the back end back to the network folder
after he got back in the office and some of his changes don't show up in the
copied version. I've tried copying both the front end and backend to the
network, I have also tried importing the table in question into the copy.
Nothing seems to work. Is there anyway to copy the correct data to the
network copy?

Would replication have worked better, or is this a design issue?

Hi Joe,

Assuming no changes were made to the network copy while the user was
away, all that should be necessary is (1) rename the network copy of the
back end and (2) copy the back end from the laptop to the original name
and location on the network.

But if other people are going to be working on the network copy while
the user is away with a local copy, you should certainly look into using
Replication. Read up on it first and plan your scenarios carefully,
because there are various subtleties that can cause problems for the
unwary. If you have questions about replication, post them in the
Replication newsgroup (microsoft.public.access.replication), not here.

On Tue, 31 Oct 2006 07:12:02 -0800, JoeA2006
<(E-Mail Removed)> wrote:

>I copied a database both front end and a back end from a network folder to a
>user's c drive for use on his laptop. I re linked the front end and
>backend.Later on, I tried to copy the back end back to the network folder
>after he got back in the office and some of his changes don't show up in the
>copied version. I've tried copying both the front end and backend to the
>network, I have also tried importing the table in question into the copy.
>Nothing seems to work. Is there anyway to copy the correct data to the
>network copy?
>
>Would replication have worked better, or is this a design issue?

--
John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.