Saving exporting field orders

[DesignDepot]

I have multiple FM databases that are all similar, but from different "seasons".

I am looking for a shortcut to save the export field order from one FM database and use that same field order on another similar FM database without having to manually reorder the field order for each database.

Thank you for any help with this.

[Søren Dyhr]

I have multiple FM databases that are all similar, but from different "seasons".

Can you in this case tell us why this isn't a flawed approach? As if straight forward searches not quite are up to make reliable subsets of data from a single base?

While being a FAQ is it indeed a common mistake...

--sd

[DesignDepot]

The databases are separate because each season a new set of data is used to build a series of new databases.

[Søren Dyhr]

Thanks I should know what season is!

So you find the establishing of a found set of coherent data an unreliable task - not something a database can be trusted ... even though it's the very core of the tools virtues as such??

The approach you here suggest is plain and simple - wrong! If you know better why ask?

--sd

[DesignDepot]

Let me restate the question. Can you save multiple export field orders in FileMaker? If so, how?

[Lee Smith]

Is your Skill "Advance"?

How about using a Script?

[LaRetta]

Hello DesignDepot,

As Søren rightfully questions, having multiple databases (or files or tables) just to split by season isn't relationally sound. It is better to have a Season field within your records (one table). Handling it properly would eliminate your current need (I believe) entirely.

However, as Lee suggests, you can use a script. You can copy the specific import script step or you can go to your new database and import the entire script. The names must match and it can be a shakey process, depending upon how closely the databases match. Overall, good design would save you hundreds of hours worth of work. :smile2:

[bcooney]

Lee. It is my opinion that many people who are using FM Advanced select this skill level. Perhaps the skill level value list should not include a word so easily confused with the product name?

[Lee Smith]

.... people who are using FM Advanced select this skill level.

and that is probably the case here.

Perhaps the skill level value list should not include a word so easily confused with the product name?

We had it first.

Actually, Stephen and I have discussed some changes to the Skill Levels, and I'm hoping that we will see some changes in them in the next Forum upgrade.

The problem is, what do you do with the existing members who have already selected this as their Skill Level?

As a part of this change, I would like to see some kind of a interactive Help on this, and some of the other questions, to aid the members in selecting things that are more meaningful.

In the mean time, anyone who has selected this as their Skill Level, should reevaluate it to see if they should change it to something else, such as Entry Level, Beginner, or intermediate.

Lee

[DesignDepot]

The season databases are individually built from new season data files each year with scripts using Apple script and Frontier. That is why there are separate season databases.

Even if you had all the seasons in the same database you still would only have the last field order export saved and I need to do three different exports for each of the three different versions of our baseball game (Board, Windows and Online).

Am I correct that FileMaker only saves the last field order export?

As a workaround I was able to create a clone copy from one of the other databases that had one of the field orders I needed and import the data into a new database. That enabled me to export the same data into the field order I needed rather than having to order it again.

[bcooney]

The Export Records script step saves the field order. You would need a different script for each type of export you require. You also need an Export Records for each table.