Export part of a larger Dbase into a new standalone file?

Discussion created by ninja on Nov 6, 2014
Latest reply on Dec 4, 2014 by Stephen Huston

I think I'm overthinking this and need to be pulled back to reality...


I have a solution running a manufacturing operation (~40 tables or so across different operations)


I need to snap-shot some of the data and compare it to a month ago for tracking performance.


This snapshot need only be two of the existing tables...and historically we've been just working from copies of the daily backups including the whole dbase.


Now the Dbase size is ~120MB and it is becoming a pain to move it around the world via just takes too long to upload and download.


Only ~3MB is pertinent to what we are trying to do, so I'm looking for a simple way to script the export of those two tables and create a two-table dbase that we actually care about for the snap-shot.


If I build the two-table dbase and export into it, no problem.

But is there a way to simply create the two table dbase via this script?

{Export "this" section of the dbase to a new file sort of thing?}


If not, I'll simply clone one of the other dbases, strip out the other tables and run the import/export from there.


Thanks for your input!

Eric T.