Message-ID: <1324832690.5.1371673055733.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_4_1711217102.1371673055732" ------=_Part_4_1711217102.1371673055732 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
I like to propose a new section Best Practice b= esides Coding Standards.
Some ideas or discussions in Coding Standards are alrea= dy belong more into Best Practice than Coding Stan= dards, like using UUID for primary key fields, or systems to use f= or passing script parameters.
I understand, there is not always a clear line between both sections. Bu= t consider this, when you rely on custom functions, you need FileMaker Pro = Advance. But the Coding Standard should apply to simple Fi= leMaker Pro users as well.
Perhaps we can mention certain features in Coding Standards and add a link to Best Practice for further explanati= on and discussion.
Some items I would rather put into Best Practice:
arnold (at) kegebein (dot) net