Jump to content

Exporting to An Archive


This topic is 5654 days old. Please don't post here. Open a new topic instead.

Recommended Posts

  • Newbies

Hi all-

I have built a relational database of about 20 tables, and am looking to figure out a way to archive records that represent "old jobs"; that is, completed, paid in full, and not to be seen again (unless i decide i need to re-import them).

Essentially, I would like to be able to select a client whom i want to remove from my database. The script will then locate every record related to that client (every job, every order made to outside vendors, every invoice element, every invoice, etc), export that data into another file, then delete it from my current database.

I realize this is a broad topic and there are probably several ways to approach this. If anyone could point me in the right direction it would be greatly appreciated.



Link to comment
Share on other sites

It would essentially be one giant looping find script where you could add all data into one field and then export that field at the end. i.e.

GoToRelatedRecords[RelatedJobs; Whatever Layout]


SetVariable[$Temp ; $Temp & ¶ & RelatedJobs::Field1]

SetVariable[$Temp ; $Temp & ¶ & RelatedJobs::Field2]

... etc.

GoToRecord[Next ; Exit After Last]


GotoRelatedRecords[RelatedInvoices ; Whatever Layout2]



bla bla bla

finish the loop

do as manny times as required

SetField[someTable::SomeGlobal ; $Temp]


and so on and so forth.

Depending on whether you want to import this again or just want to view the txt files later, you might format the output differently.

Link to comment
Share on other sites

I would think more of just creating a clone of your working database, all the relevant tables. Then creating a master script to go through all the tables, finding those older client records, and importing them, 1 table at a time, into the archive table. Then deleting the records in the master file.

After finding older clients (not sure exactly what criteria you'd use), you could use the new Go To Related Record option matching [x] All records in found set. That would get you the found set for all the older clients in the other tables.

If your relationships are set up correctly to [x] Delete matching records in related table (the child table), then you could just delete the clients at the end of the script, and all their related records would be gone also (it can take a while).

Obviously you want to experiment on test files until it works flawlessly, and backup immediately before running, every time. It's a little dangerous.

Another question is whether you really need to do this. Are the old clients never coming back? Are there really so many? etc.. But if they're never coming back and there are so many, it may be worth it. Lean and mean is good.

Link to comment
Share on other sites

Alternatively, do as Fenton suggested, but rather than making a clone, export the records to be archived from your primary file and trigger a script in the secondary fm file to import those files, then proceed to delete... or export delete, export delete, export delete, import. Up to you really.


Link to comment
Share on other sites

This topic is 5654 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Create New...

Important Information

By using this site, you agree to our Terms of Use.