scs wrote:
Thank you. I don't anticipate any more than two people using this at
a time. It's really going to be used primarily by one person. I
mainly just want them to be able to use it while I'm working on the
front-end. However, it will probably remain split in the end and
used by two folks occasionally at the same time.

I'm looking for a way that a user could enter the front-end and,
through a very user friendly interface, backup the back-end. If I'm
understanding you correctly, this would not be possible because the
backend would be in use at that time by that user.

I was hoping the user could make a quick backup of the data from
within Access before making a bunch of changes. I guess I'll have to
develop some other means outside of Access. Is this correct?

If your app is split then you can still do this from the front end providing
that no bound forms or reports are open at the time you do it. Testing for
the existence of the LDB file will let you know if any bound objects are
currently connected to the back end. When it is not there then it would be
safe to copy the file.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com