Same sort of task...but not by script alone...not sure if there IS a way to do that by script alone...
I snapshot a few tables of a much larger Dbase periodically to have a snapshot of inventory at defined dates.
I put the stripped down dbase I wanted (blank...no records, but with import scripts that launched on opening) in a container field in the hosted dbase.
From the hosted dbase, it exported the "mini-file", opened it, and thus launched the imports. (and set a flag field so the import didn't happen every time).
Got the idea from several here, including Mike Bergie, and it has been working well for months now.
are their any container fields in the table you want to "backup"?
Mine has no containers...not sure how to make that work...
Are yours stored externally where you can just set a pathname? Or is the image within the Dbase?
Not sure it makes a difference...unless it's stored external secure...
I'm currently storing the image in a container field in each record. If I had to though, I could store that image in a related database that isn't part of the backup.
Ok, I've removed the container file from the table that I want to backup.
What's the best format to export the records in? I don't want or need the users to be able to open the exported file. I only want them to be able to import their backup, if they need to.
Thanks for all your help so far.
Assuming you are following the method I am using...
Don't export the records.
Export a single table database (you'll have to build this first) from your "live" file.
I just store the blank "recipient database" in a container in the live dbase.
Open that single table database
Import the stuff you want from the live dbase into your single table dbase.
i would choose .mer file format but thats just me. their is no best format. the only consideration iis xls format because i dont think a single cell can hold more than 255 chars. That may have been a restriction with older excell tho.
Thanks again everyone for your help. I believe I have this sorted out now