How large? (#fields/columns? size of data? #of records/rows? or all of these?)
And are there ways to convert calculations to auto-enter or scripted enter, so that they need not be recalculated just for export?
Also platform(s) and version(s), including FMP/FMPA/FMS may or may not give clues as to what's happening. Can you provide that information?
Do the export as a Perform script on server or set it up as a sever scheduled script?
The table which I planned to export has 632 fields where most of the fields belongs to Calculation type.
I have ignored Calculation fields and exported the data where it was fast. Where as including calculation field at the time of exporting consumes more amount of time.
I am doing this using Filemaker Pro, Export records as excel option.
There is no way to convert the calculation field into suto serial or script enter
Please suggest me if there is any alternative approach for this to do.
Calculations are going to take longer.
-- sent from myPhone --
Does there is no solution for this case ?
Thank you for your posts.
Are all of the 632 calculation fields stored? That is, in the Options for the calculation field, is the checkbox "Do not store calculation results -- recalculate when needed" checked? If so, then each record needs to re-evaluate the field at the time of export.
How many records are you exporting ?
Is it possible to move the whole database to a SSD disk before exporting ?
while not having a helpful suggestion for you, 632 fields in one table indicates a design problem in my opinion.
true, even if they were only 0 and 1, an Excel table with 600+ columns is not something I'd fancy to interact with.
Why export to Excel to start with, anyway ?
You are right. The option is enabled in the calculation field.
Hope unchecking the option helps not to store the exact data in the respective fieldss.
Can you tell me whether is there any solution for this to reduce the export time ?
I am exporting nearly 2 lakh records which is present in a single table.
Can you please tell me whether moving the db to SSD disk resolves this issue?
FileMaker, unfortunately, is slow at number crunching, so there is no easy solution
If the export is just a data dump, remove any Summary fields, and summarize in Excel later
However, if you are trying to export a report, with multiple sub summaries, of un-stored calculations, then you are stuck waiting, and waiting
And any calc that uses related data is the worst
Keep in mind that only one or two calculations may be the bottleneck. It might pay to experiment, to find the slowest ones, then run a script, perhaps the night before, to set those values in number fields for export
> Can you tell me whether is there any solution for this to reduce the export time ?