I started using databases *after* learning about relationships and being a programmer. So, I avoid repeating fields entirely. Since this feature has persisted through 5 generations of FM that I have used (3-7), I guess it has some use. Can someone give me an example or 2 of a good use of repeating fields?

Here's a highly-respected whitepaper that has a page or so on that topic:

http://www.foundationdbs.com/Downloads/WhitePaperForFMPNovices.pdf

Since we with you ain't in the corruption of youth line of business, you seems to know your stuff! Therefore can these two last templates be used to expand your horizon without much cautioning:

http://www.dlsystems.fr/tips_tricks/tips_tricks.html

(it's only the two last ones fitting this topic, although it's quite a capasity in the filemaker community, who showers us with insight)

--sd

Hi,

I use them anywhere I need a static array, but never for data (text,number,date,calc,etc)storage. However, good for container fields, since they are graphic and many times a part of the interface.

They are carried along for two reasons, IMO.

1. Legacy files used them in exchange for the RDB model.

2. Very handy for static arrays.

HTH,

Tim

... + Backwards compatibility

Hence the word "Legacy" ...

--sd

... Oh right