Field name caution
From when I started with FM, I have been careful not to use spaces when creating field names -- opting in general for CamelCase or "_" to indicate word separation. This was due mainly to the paranoia induced by some documentation and references.
However, repeatedly I have noticed rather liberal usage of spaces in field names in FM sample files, third-party solutions, and even here in this forum in posts by very experienced and respected developers.
So, my question:
Is there really a concern about using spaces in field names? (Or layout names, or script names, etc.?). If so, under what circumstances? SQL-related?
In general it is not a significant concession to make, but using spaces does present a cleaner look when the field names appear as column headers in Table View.