Quote: I was just trying to avoid transferring duplicate records via email.
That may be a different story. I did not understand the problem before. The issue is the transfer time of the data.
In that case lets think about this.
We know:
It is easy to have a field in QA to identify what records are new or modified each day.
It is easy to export just those records from QA.
If it is a relatively small percentage of all the files so that transfer of records would be considerably shorter maybe its worth thinking about creating a routine using XPOST.
Unfortunately I know very little about xpost but on page 38 of the Sesame programming Guide it says posts the entry value to the target element on a match between the key element in current database and the external yada yada.. default operation is Replace.
In basic terms imagine transferring the small file then
Create a routine something like this:{I am reaching here. There may be a cleaner way to use Xpost)
import data into a temporary database, that database uses xpost to match record id in good Sesame database and it marks a field in your good Sesame database that is used as a way to identify the record for mass deletion.
Then the mass delete is ran
Then when the exported file is imported all would be in sync.
I hope that makes some sense. The key here is how much time is saved by transferring just the modified records as opposed to all the records.
Let us know if it is a significant amount of time and if it is we can learn more about xpost or ?
Robert