OK, I have run into another roadblock. Maybe you all have some ideas.

To re-summarize, I have a large FMP6 database of one page medical  
reports, that I want to export in the formatted form that I would  
normally print.

I need to name the file of each exported report with the Patient  
number and date of the report so that it can be imported into a  
commercial electronic medical record program.

I have been able to run a script that copies each report in Preview,  
and then pastes the report into a container field. The plan was to  
export the container field and the date and Patient number fields into  
FMP12 where I can export the reports with the above filename convention.

Problem is this: There are 18,000 reports, and by the time I have  
converted 3750 of them, the file size reaches the maximum of 2gB and  
the script stops.

Short of breaking up the job into 5 pieces, does anyone have any ideas  
on how to do this?
I have another file to convert that has 163,000 records, so breaking  
it up into that many pieces will be an issue.

On Oct 16, 2012, at 4:09 AM, Steve Cassidy wrote:

> On 15 Oct 2012, at 12:55, Jay Erlebacher wrote:
>
>> Your advice seems very practical and do-able. Steve.
>
> Jay
>
> Since no-one has suggested other ways of doing what you want, I'll  
> add a couple of thoughts I've had:
>
> – Conversion may not be completely straightforward; it's quite a big  
> jump from FMP6 to FMP12 and quite a lot of functions have changed in  
> small ways.
>
> – If you decide to purchase a copy of FMP12 in order to complete  
> this task, you may still want to store images of your reports in a  
> container field BEFORE any conversion to FMP12. This will ensure  
> that the report is preserved exactly as seen in FMP6. (Or perhaps  
> you could take this as a fallback process in case you do see issues  
> when/after converting the full database.)
>
> – If you take this approach, I'd suggest first exporting only the  
> data you need for the image export (ie the new image container and  
> the patient ID or whatever) to a new FMP6 file. This will be a  
> simple, uncluttered FMP6 file containing only these fields (and no  
> scripts, etc). Then you can convert this file to FMP12, where you  
> would prepare the export of images with suitable filenames. Your  
> main import of ordinary alphanumeric data to the new system would be  
> directly from FMP6.
>
> – Make sure you keep secure backups of your data before doing any of  
> this. And also keep copies of the file(s) along the way, so you can  
> always go back a step without having to do everything again!
>
> Steve