Kbase P25824: Dynamics. Fields Naming Convention.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
26/05/2003 |
|
Status: Unverified
GOAL:
Dynamics. Fields Naming Convention.
FACT(s) (Environment):
Dynamics 2.0A
FIX:
Use the same name for fields in different tables if they can be used as join fields, such as Customer.CustNum and Order.CustNum. If the fields cannot legitimately be used as join fields to associate records in the two tables, then make the field names different, even if the information is from the same domain of values (such as ShipToNumber vs. BillToNumber). This convention simplifies query syntax to take advantage of the Progress <table> OF <table> construct. It also makes it possible for modeling tools such as ERwin, and other tools that need to make associations between tables, to make the right determinations as to how tables can be related.
Dynamics can take advantage of table and field names that are a meaningful string of words, replacing the standard delimiter (whether underscore, capitalization, or possibly something else) with a space to provide a meaningful name to insert into a message text, for example. Also, if you use the ERwin modeling tool to define the database and generate the Progress schema, macrocode supplied with Dynamics will define an initial label for every field, formed from the field name with the delimiters replaced by spaces. If you observe the naming convention, you can save a lot of time completing the definition of all the entities of a new database schema.