Hi,

Would someone know how to write a script to find the next empty field in a list of repetition fields?

Yes, ... but you're probably barking up the wrong tree here. Bruce have a rule here that says, if you don't know how do it with repeating fields is it because something is more appropriate - Portals and relations is the name of the game here usually, with very few exceptions really!

Study this: http://www.databasepros.com/FMPro?-DB=resources.fp5&-lay=cgi&-format=list.html&-FIND=+&resource_id=DBPros000717 or Comments Invoicing template, eventhough you task isn't particular invoicing ... falls a lions share of all database issues inside a scope of 7 types of relations, and flat-filing ins't one of them!

--sd

LastRepNumber ( repeatingField ; maxRepeat )

http://www.briandunning.com/cf/472

This was the method I thought about, but when the question is made as it was here, is there a myriad of ways to interpret the objectives, due to their absence.

It is a concern of mine if this is used to find first available slot for say, an appointment ... this is way too much as if the Interface were the main issue with databases.

Appointments or bookings are much more in this direction:

http://www.nightwing.com.au/FileMaker/demos7/demo705.html

All in all could the question be reformulated, where exactly does Daniele's approach actually really make sense? I my humble opinion is there only perhaps a speed issue which could talk in favour for the deployment over genuine relations?

--sd

Hi,

Would someone know how to write a script to find the next empty field in a list of repetition fields?

Generally, repeating fields should be avoided, in favor of using a related child table. Repeats present a lot of disadvantages, and this is one of them, a problem that doesn't exist with a proper related table. What is the purpose of the repeating fields in this case?