Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

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

Recommended Posts

Posted

I have a database with 200 records and need to export them to 200 individual tab-delimited files. Unlike the save-records-as-excel command there doesn't appear to be any way to export just the current record, then go to the next one to step through the entire database Any suggestions?

Thanks.

Colin

Posted

There are a couple of methods to do this. The easiest is likely the New Window method. Each window has its own found set. An Export uses the found set of the active window. So, create a New Window. Then, Show All Records, Omit Record, Show Omitted Only. You then have a found set in that window of one record, which you can Export. Then close the window, go to the next record, repeat.

You will need a unique name for each of these exported files, as they are going into the same folder (presumedly). That could be done using a unique ID of each record, as part of the file name. The entire file path (or a relative file path) would need to be set into a Script Variable, then used in the Export dialog file path. This would all be done (over and over) within a Loop thru the records, using go to next record, exit after last.

There is another method, which would do similar, but instead of a new window, it would "save the found set", then restore it. It is a little trickier, but has an advantage that it does not flash so much (which new window does). But that's likely a minor point.

Either method could use Go To Related Record [ unique ID self-relationship ] to isolate the 1 record. But that's also a minor point. The Show All, Omit, Show Omitted technique may add a new record to the found set; but that likely would only matter in a high volume of created records environment. The Go To Related Record technique avoids that.

Posted

Your "New Window" method is the perfect solution. The minor cosmetic issue of the flashing windows as they open and close with each step through the database isn't important as I'll be the only one to run this script. Setting the file name to a variable so they don't over-write each other takes care of actual export step.

Many thanks for your help. It's a clean and easy to implement solution.

Colin

This topic is 5540 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.