You are going to need to transform rows into columns. You can move the data from your current tables into an intermediate table configured for export purposes or you can use relationships and calculation fields (or they can use ExecuteSQL) to move your answer data into columns so that you have the needed structure for export.
There are probably as many ways to do this as there are FM developers. LOL!
You are wanting Pivot Table or Cross-tab (cross tabulation) reporting, which is not native in FileMaker. However you can search for 'filemaker pivot table' or 'filemaker crosstab report' (on this forum and any search engine) for some of the ways others have done this.
1 of 1 people found this helpful
There are also some third party tools for exporting to excel. You might investigate those to see if any will transform rows for columns as part of the process.
Thanks for the input - just in case someone finds this in the future, figured it best to explain what I've decided to do.
I am a Mac guy, but will be working in a mixed environment on this project. I have a handful of users that want the data exported to excel and refuse to touch FileMaker, so that put me in a bit of a bind on how to deliver what they wanted.
I had considered developing an export with XML and using XSLT to transform the data into what I wanted in Excel, however Excel's mac versions don't support XML while the PC version have complete support for XML (Ugh Microsoft!).
After much research, I found plugins from both MonkeyBread and 360Works, and I'm going to use one of their solutions since it seems like a much less painful route by keeping all of the work within FileMaker rather then to have to build something else from scratch. Thanks again for everyone's input.
I have to disagree with XML doesn't work with MacOS Excel. I use it all the time. You can't create .xlsx, but .xls should read just fine.
Sent from miPhone
In manage database create these fields.
Then create two scripts as follows
#3 and a third script to find only the ones you want for export to xls
(make RecordID a button performing third script)
Layout one with all records:
Layout two with RecordIDs only
These records can be exported as cvs or xls whatever you want.
You really shouldn't use Copy & Paste unless it is essential to the task at hand (ie paste an image from an outside source). The combo of Set Variable[ ] and Set Field[ ] is preferred for a number of reasons.
You also don't need to create fields to hold the found count and calculate 1/3 of it, respectively, when you can calculate the result in the script, store it in a variable and use that to control the loop.
Finally, you could replace your lines 6-15 with
Set Field [ Questions::Q_ID2 ; GetNthRecord ( Questions::answer ; 2 ) ]
Set Field [ Questions::Q_ID3 ; GetNthRecord ( Questions::answer ; 3 ) ]
which in this case is even better than SetV/SetF because you have a known data structure (or a naïve approach ...)
or for this even task
Set Variable 
would be preferable to copy/paste!
I should have been more specific. In the PC version of Excel, there is a special toolbar specifically for mapping XML files and managing them within Excel. The toolbar and functionality is missing in Excel for the mac - though you can still open the files there.