Based on a bug discovered by Federico Severin

bug\'s joke.zip

strange - when i create a new record with new data it evaluates correctly for each?

Because you'll need to fire the script that sets the rep #0

that's evil :evil:

Yes.

The bug must be on the unique way to set that repeatition: using the Replace Field Contents [ ]

Nor Set Field [ ], neither Set Field by Name [ ], can set that rep.

Continuing to joke, you can set any number of repetition ( 0 or even negative ), but there will always be a single repetition that will occupy the second position in the result of the function List ()

Note that this doesn't have to be a repeating field. If you perform a replace on any non-rep field; but use an invalid rep (zero; negative; or emtpy) in your replace operation, you will get a damaged index. Actually you will get an index that holds the new value, but the index shows a question mark. However if you search for record containing the replacement value, you will find them.

This fact supports my hypothesis that the problem is all in that script step.