Hello

I am currently cleaning up a database, where ways to many field got created - an now should be removed in order to make it snappier.

Now, if I delete some fields, the export records (to tab files) doesn't keep the corect fields.

How would you handle with that issue? I'm quite confident, that the OS Version is not by any relevance. Is that right?

Cheers and thank you for your feedback

If clumsy means repeating fields have been used to emulate a relational structure, can you use the Layout object in applescript to transfer data between two bases where the sequence are identical.

Even though it not is said directly here - is it the way it's done:

http://tokerud.typepad.com/filemaker/2006/06/new_record_with.html

...however must a switch be made between the two bases in between the two lines....

--sd

in fact clumsy means that different developers with different skill levels developed the database over the years.

how is the export sorting stored? i'm quite sure it is based on some kind of information, but what info is this?

one easy solution (but not a clean one) could be to modify the field which are not needed to globals, and possibly mark them in the field name as old_one, old_two, aso.

the applescript solution is not suited to solve my issue (or i did not understand it...)

cheers

I'm guessing that your exports are scripted. Correct? If not, ignore this.

Exporting from FMP can be a nightmare if you are developing or, worse, modifying a DB. Every time, you delete, add or rename a field, you need to re-code the scripted export. Otherwise, you are likely to get output you were not expecting. As far as I'm aware, there is no simple solution to this. If there is, I'd love to hear it.

yes, it is.

is there an end to this nightmare speaking of FMP versions?

how do you folk deal with this?

could a I/O database help (corresponding names)?

I would keep to my suggestion, make a layout in both solutions which carries the same tab-order and let applescript monge these, since every other kind of export would need exports in plural to maintain the referential integrity in related tables.

Although this might have it's justified use:

http://www.nightwing.com.au/FileMaker/demosX/demoX06.html

...is it still "horses for courses"

--sd

many field got created - an now should be removed in order to make it snappier.

Are you sure that it is the number of fields that is the problem?

I never, never DELETE a field in a database, that I didn't create. There are too many problems that can come as a result of a missing field. Just rename the candidates using a prefix of ZZZ (or something), to the existing name so that you can find it later if needed.

There are White Papers on how to Migrate a file or files that can be of help to you. Here is a FileMaker Tech Article that lists a few to get you started.Link. do a Google Search for Upgrading a FileMaker file and you will get a lot of sources.

is there an end to this nightmare speaking of FMP versions?

Each version is a little harder to learn, but provides more tools to improve your products.

how do you folk deal with this?

It is not rocket science, it does take a lot of time, and nobody said that it was easy.

Lee

Edited December 9, 200916 yr by Guest