I think you mean that you have a table view and you want to swap the columns for the rows.
Such a change, while not trivial, is at least possible, but whether it is practical or not depends on the design of your database.
"a couple of hundred fields" is a LOT of fields to define for one record. That may, in fact, be necessary, but it is also possible that you should split this up into multiple records where you have one record with many fields. It may even be useful to add related tables for some of this.
Thanks for your response.
'I think you mean that you have a table view and you want to swap the columns for the rows.' - Exactly!
Yea, lots of fields. Mostly Pass/Fail test results. One record per build per tester.
Each test result can be a related record instead of a separate field in the same record--that's an option you should consider carefully as it can offer considerable improvements in overall flexibility in how your system functions and what kind of reports you can produce from your test results..
As a quick fix, I suggest not trying to set this up in table view. Use either form or list view and you can arrange and position your fields on the layout in a vertical orientation instead of horizontal. Using list or form view, you can use multiple rows of fields for the same record.
Arranging in list view would be a manual thing or is there an option somewhere to have FM do that for me?
Thanks again for your help.
It's manual. It's more work, but table views are rarely sufficiently user friendly for general use. They are best used, in my opinion as "debug" layouts used by the developer to get quick flexible overviews of the data.