When creating table field names, make sure these names are unique enough that they do not conflict with already existing 4D commands. If the table names do conflict with 4D commands, those 4D commands will no longer be tokenized within any of that specific table's forms. For example, Table_1 has two fields named date and time.



Now whenever the 4D commands Date or Time is used in any of that table's forms, neither commands are correctly tokenized which would be typically bolded in green colored font.



To resolve this issue, simply rename those fields with a more unique name, underscores, or camel case to avoid conflicting with any existing 4D commands.