This is not exactly that you were looking for, but if you need to have a bit
more control over things, this will work great.
I have both a clients production pathcode and demo jr. on one machine.
Often I will copy the folders under the Prod pathcode to my demo pathcode,
except for the data directory. However, when I do that my demo junior is
not aware of new objects, due to there being no record of it in my demo's
F9860 tables. To get around this I created a new datasource/OCM mapping to
point to a new file in my data directory. my ocm mappings tell demo jr to
get the f9861 tables from that other database instead of the jdeb7.mdb With
that setup I can quickly export the production F9860 tables into the new mdb
with issue.
As far as just importing and exporting I have never tried that.
AW