Field ordering in a table
-
is there an advantage to laying out fields of certain data types in a particular order? For example, in MS Access 2007, is it best to have all Memo fields at the end of the table definition? Thanks, JJ
-
is there an advantage to laying out fields of certain data types in a particular order? For example, in MS Access 2007, is it best to have all Memo fields at the end of the table definition? Thanks, JJ
-
-
is there an advantage to laying out fields of certain data types in a particular order? For example, in MS Access 2007, is it best to have all Memo fields at the end of the table definition? Thanks, JJ
While there is no technical benifit I have always followed these rules Primary keys is the first field (I almost never use complex keys) and is usually an identity or a GUID inder duress Foreign key fields (you know all this ####ID fields) Primary description field(s) All other fields Modified and ModifiedBy are generally the last 2 fields on most tables.
Never underestimate the power of human stupidity RAH
-
is there an advantage to laying out fields of certain data types in a particular order? For example, in MS Access 2007, is it best to have all Memo fields at the end of the table definition? Thanks, JJ
Even though it may look nicer to have columns sorted in a particular order, sooner or later you will have no influence on the order any more. For as far as I know it is not possible to insert a column inbetween to existing columns without dropping the entire table and recreating it, which in most large live systems is a big no no as it cost way to much time to do.