What is the difference between "multiple columns" and "one continuous horizontal table"? Sounds like the same format to me.
I am not aware of any loss of feature here, but then I am not clear as to the difference between these two options.
That said, I strongly encourage you NOT to use a repeating field for this. You can set up a related table of missions flown records instead of the repeating field. Data from such a related table can be organized into columns using one row portals and there are several different options for controlling which portal displays data for a particular mission.
I will check with my associate about portals. Our biggest problem is that his version of FM and mine are not compatible. I can not "dumb" my version down to him and I have to manually update any changes he recommends. I will dig through the help files to review how to use portals.
I'm attaching a screen shot of my relationship map and would appreciate any comments or suggestions for changes/updates. I'm a recently retired software engineer but have very limited databaase experience as my background was with embedded systems.
I think you mean multiple rows and columns at the same time. I never knew that was possible, though.
I also know for printing purposes, if you have the related table instead of the repeating field you can
- Put the field on the layout.
- Make the layout almost the size of the field.
- Go into Layout mode
- In Layouts -> Layout Setup -> Printing
- Then change the Column amount
That will create multiple rows and columns.
"We have set the number of repeats at 60 and would like to have multiple columns rather than one continuous horizontal or vertical table. In the earlier version this was possible, but that functionality has been removed for FM 12."
You have the same functionality in both version.
IE you could have 6 columns with 10 cells, because you can set the starting and ending repeatition number of each column.
From the look of your relationships graph, I recommend learning about the Anchor Buoy method of setting up groups of table occurrences that minimize the confusion due to ending up with a "spiderweb" of relationship links.