AnsweredAssumed Answered

Splitting a database - Creating a clone and importing/transferring records

Question asked by justtivi on May 9, 2014
Latest reply on May 9, 2014 by Mike_Mitchell

As a way of archiving and sharing disconnected data, I'm trying to create a script to, in essence, export a set of records away from the main file onto a scripted creation of a clone.


After creating a clone, I'm lost on how to migrate a current found set and related records to the new file, as variables don't transfer over. A script trigger on the clone can't pick up variables created from the original file.

 

A script-trigger on the clone to import records from the current found set that is open on the original file seems to work for one table, but when I create a second script step to import records from a related table, I can't specify a different table without a dialog window. I'm trying to map out the imports without any perform dialogue windows.

 

 

Hoping to find a way to do this all natively.

 

Is there a file-to-new-file way of doing this, carrying information to a new file?

 

My last resort option it seems to me might be some crazy utility table where I copy everything on the original file, then allow an automatic import script trigger on the new clone to import the utility table data and loop through to create new records and parse out the data throughout every table. There must be an easier way.

Outcomes