We plan to split our ACCESS application into front end and back end so we can
have a more reliable multi-user setup. Currently , we just have the unsplit
application in the server so they can share it.
We also have a copy of the same application for stand alone use of our data
analyst which we update once a week (she does not really need realtime data
in fact she can afford a once a week update. At present, we just update her
copy once a week by copying and pasting the application in the server to her
workstation. We do not really want to link her to the shared versions as she
might change some data.
What is the best approach to update her tables when we split our
application. We just plan to have her own unsplit version, but how do we
update her tables without linking her to the backend DB.
Thanks in advance.
Douglas J. Steele - 08 Mar 2006 22:59 GMT
Why not make a copy of the backend database for her?

Signature
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)
> We plan to split our ACCESS application into front end and back end so we
> can
[quoted text clipped - 16 lines]
> update her tables without linking her to the backend DB.
> Thanks in advance.