I am a little unclear what you are doing.
There are several functions not listed under "Repeating functions"
List() uses "non-blank" values, so may not help, if any of your repeating fields are empty.
There are alternate ways to address repeating fields:
Also, you may wish to study using related data rather than repeating field data:
And consider converting repeating fields to related data (note there is an "export" part here that may help)
Custom functions may help:
http://www.briandunning.com/filemaker-custom-functions/ (search for 'repeating')
Can you post any screen shots?
Basically, I'm putting all repetitive values into one field, so if we have:
If I put this into my new format, it becomes 1|2|3|4, or 1;2;3;4, depending on what code you want in between.
But I also need to rename
1 -> A
2 -> B
3 -> C
4 -> D
So I get A|B|C|D. And that's what I need.
The A|B|C|D is what the other program asks from me.
It's a combined breakdown of the repetitive field and rename text action.
Problem here is that I have 20 repetitions, besides 44 values already which can be used in all repetitions. So it multiplies.
I'm now thinking about making another table with these 169 values (i'm currently only using 44 out of total of 169) and that I use a lookup first in a new variable, so that I can get codes, before getting into the rest of the process of creating the A|B|C|D thing.
Take a look at Extend() to possibly make the "conversion" first into another repeating field which you then use for your calculation.
A probably better approach is creating a table that holds the texts, including their abbreviated versions, then (instead using fields in your main table) assign the desired texts as records into a child table, like:
MainTable --< TextChildren <-- TextTemplates
This will simplify the entire query from the context of MainTable to
List ( TextTemplates::abbreviatedVersion )
Yeah, I was thinking about something like that as well. Because now I want to do 2 things at once. Which works for a more simple approach with 5 repetition, 9 possible value approach...
In the meantime I created another table. Then I insert data from this table into my file, and then I can export more easily...
Problem was that I wanted to do two things in one action. This should work...!
The only thing now is that I need to know what to export, now that I have some more possibilities. But that is out of topic...