Thank you for your post.
I am able to replicate the issue under Windows 7. The issue does not occur under Mac OS X 10.10.3.
I have sent your post along with my findings to our Development and Testing departments for review. When I receive any feedback, I will let you know.
Well we've been telling people that repeating fields are rarely the best design option--having started becoming obsolete with the release of FMP 3.0, but this is probably not the best way to encourage folks to stop using them.
An entry in the Known Bugs List has been linked to this Issue Report. Any Comments/Questions/Suggested Corrections should be posted here or in a new thread. Please do not post such comments to the Known Bugs List thread.
Sorry Phil, but I have to disagree here. Repeating fields are only obsolete where a related table is more appropriate, like for invoices and invoice lines. But there are many other use cases where a repeating field is just perfekt. Btw. this bug is a really big one, it can do huge damage not only to the programming but especially to the contents of the database. One can easily set the repeating count back to the initial value but once the first changes are committed, all data in the dropped repetitions is deleted irretrievably.
First off, I was making a JOKE. I do find repeating fields useful once in a great while.
Second, I agree that:
Repeating fields are only obsolete where a related table is more appropriate,
But I will politely disagree from that point forward as IMO, a related table is more appropriate in 98% of all places where you might use a repeating field. They are very convenient for getting a row of related fields on a layout all sized/formatted the same, but then, when you go to work with that data, you find yourself trapped with very awkward inefficient solutions when you need to set up reports and analysis of the entered data.
Where I will still use a repeating field?
To create a progress bar type feed back with conditional formatting filling in the repetitions of the repeating field (which is a calculation field with repetitions.)
To manage a small number of (often) global image icons
That's about it for me though you may have thought of uses for this that I haven't.
You make a good point on the "risk level" of this bug--I've increased the risk level to "high" for that reason.
PS. a repeating variable, on the other hand is often useful....
Our Testers were able to replicate the issue under Windows, and the information has been sent to Development for review. When more information becomes available, I will let you know.
Sorry for the late response, but this appears to be fixed in FileMaker Pro 14.0.2.
For other issues addressed in FileMaker Pro 14.0.2, see: