Hi
The main problem you would have is in maintaining any relationships - well
it's not a "real" problem it is just that if you google this, most of the
answer will remove the realtionships and basically "mess up" your DB. Mind
you in you're just using the access DB to store a sinlge table (eg. a list of
passwords, or dates, etc) then this will not be a problem.
You can use something like
DoCmd.TransferDatabase acExport, "Microsoft Access", "Path to DB.mdb",
acTable, "TableA", "TableA", structureonly:=False
DoCmd.TransferDatabase acExport, "Microsoft Access", "Path to DB.mdb",
acTable, "TableB", "TableB", structureonly:=False
DoCmd.TransferDatabase acExport, "Microsoft Access", "Path to DB.mdb",
acTable, "TableC", "TableC", structureonly:=False
There is not much difference in exporting and importing (there are "some" -
just not many) so have a look at an answer I gave a while ago and feel free
to copy the code if you want. You will need to amend it to "send out" rather
than "bring in" but thats quite simple.
http://groups.google.com/group/micr...roup:microsoft.public.access#786781a92a2adf02
If you need more information you could post a question in the access area as
this is not really an FP problem
Good luck with your project