[You can use the Linked Table Manager to remap the linked tables in your
front-end to the correct location.]

Are you referring to my home computer? I ask that because everything works
properly at work.

[I'm not quite sure I follow what your co-worker did.]

The J Drive was not accessible so he had a copy of both the front and back
end databases on his F drive. He entered new data and somehow it wound up in
the back end on the J drive. I don't know if that explanation helps.

[First question is are both your front-end and back-end located on the
server? They shouldn't be. Only the back-end should be there: each user
should have his/her own copy of the front-end, ideally on his/her hard drive.]

OK, that might be the key to my confusion. I'm not quite sure what you mean
by their own copy of the front end. There are 2 files on the J drive:

registration.mdb
BackEndregistration.mdb

It sounds as if the source of my confusion is the fact that everyone is
sharing the same FRONT end on the J drive. Is that correct?

How do I solve that problem? What do I do with the registration.mdb front
end? Do I email it to each member of our team?

If that is the case, what should they do on their end?

I hope I'm asking the right questions.

Thanks,
Robert

Doug:

I think the light bulb finally came on in my head and I understand what
you're talking about. I updated the front end this morning and emailed the
new version to every member of our team with the following instructions.

1. Delete the old version of registration.mdb.
2. Copy the new version of registration.mdb to your local C drive or your F
drive.
3. To access the database, simply open registration.mdb on your C or F drive.

If I understand this correctly, when they open registration.mdb on their
local hard drive, it will be linked to the back end mdb on the J drive. We
don't need a copy of the front end on the J drive.

Is the above correct? Did I finally get it?

Thanks,
Robert