Field Label Peculiarity - Association Break

[LaRetta]

If you Insert Field and check the box 'Create Field Label', FM will nicely do so. Everyone knows this but did you know that, after creating a field label name in this matter any subsequent changes to that field name in Define Database (vs. 7) and Define Fields (less than 7) will also change the field label names everywhere it's been used throughout your solution? Some Developers know this so create their own field labels to avoid this bug. Some Developers know this so use this feature to save time having to then change the name everywhere.

I borrowed the idea of FM native 3D titles, headings and field labels from Ray Cologon (CobaltSky). By using FM native headings and labels, I get the benefit of gorgeous labels without the overhead associated with standard graphic elements. I discovered the above feature/bug and decided to use it to my advantage and now create all my text this way. I created a new file (LabelMaker) whose only purpose is to allow me to mass-produce the exact 3D effects and colors to be used throughout my solutions. Anyone interested in this technique should refer to Fast & Gorgeous 3D Text

Something I just discovered about this field label peculiarity...

You can break the association between the label and the field itself so it no longer changes when its name is changed in field definitions! This again, is good and bad.

Example: You allow FM to create the label (relying on it changing if you change the field definition name) then begin moving your elements around. But you split the label from the field (moved them a ways apart by 200 px or so). Ooops! It will fail to change if you change the field definition. Even if you move it back - once broken it stays broken. So if you would like FM to create the field name and then preserve the name (so it won't change) just drag it away from its field, save your layout, then go back and place it next to your field again. If you want the name to change, be aware of this and keep them together while moving them.

This 'breaking of association' intrigues me and makes me wonder what other layout associations may behave similarly. A while back, JT helped me with a repetition calculation for The Field Factory. He mentioned confusion on why his calculation wouldn't update the field labels. Now it's clear why - the association had been broken.

I hope I'm not the only one that 'gets off' on this stuff. Being aware of this peculiarity might be useful at various times and might save headaches at others.

LaRetta