One solution is to have another table or file specifically for Exports with the proper field names. Depending on how you deal with exports you can generate the export data by relationship, import, or record creation. After export the data is deleted from the temporary export table.
Reflecting that back for clarification:
1. I have my current field names/ data.
2. The desired data set from 1. is exported to another table (or file) that has user-friendly field names.
3. Export to Excel (or whatever) from 2.
4. Delete records in 2. (either at the end of the script or beginning of the script).
Is that correct?
Sounds about right. There are a few ways to get data in the Export table. Some consideration needs to be made if you have related record data in the export. If it is a simple single table export it is easy.
FM15 TruncateTable is super nice for this.
The advice you got here is correct. I will just like to add that this is why we try to use "natural" names for fields.
In most of our solutions the users will never see the file names, we build functionality for searching/sorting etc.
But if you want the user to sort via the build in Filemaker functionality it is nice if they can recognise the field names.