1 of 1 people found this helpful
If you're the primary developer, keep what you're familiar with, filemaker is relatively forgiving of any naming convention.
In Filemaker, you should try and avoid spaces, special characters, numbers and reserved words:
as part of your field and table names. This will make it easier to reference those later.
Personally, I prefix all of my fields with their type so that they group nicely when I sort by alpha:
a__kp_primaryID for primary ID
a_kf_parentID for a foreign key
c_fullName for a calculated field
s_totalCost for a summary field
zz_createUser for a creation user auto-enter field
Which way is preferred?
I'd say the answer is: use whatever nomenclature works best for you.
Mike, thanks for the advice. For the record, I don't use spaces, special characters, or the like in field names.
Then all you should need to worry about is reserved words. FileMaker will auto-bracket fields that are oddly named (e.g., a field names “2015”), so if you see curly braces in some of your calculations you’ll maybe want to change those field names.
Leading underscores can also break in the ExecuteSQL() calculation, and reserved words apply to that calculation as well.
There are many ways of doing this. Take a look at the filemakerstandards.org website for good suggestions on how to develop in FileMaker.
Sent from my mobile device... Please excuse typos.
more than just that: Only use standard ASCII set, no spaces, no underlines at the beginning of a name (sql...). Besides of this: As Erolst mentioned - use whatever fits (-:
Just had a look, and while I agree with what Mike write (or any similar consistant prefix) including the zz_ which we use for all fields that are basic/house keeping fields in all tables, I found that standard data fields was forgotten here.
All ordinary fields we would use natural names for. Like: