SQL Reserved Words |
  
|
SQL Reserved Words |
|
This is used to store all the SQL reserved words that will not be used for table, column or key names when DMC builds tables. You can add edit or delete any of them to accommodate your favorite version of SQL or desired company standards.
You have TWO LEVELS: 1 is compulsory (used by DMC during cloning tasks) and 2 optional.
If you want DMC to consider a level 2 word a reserved word during cloning tasks, double-click on the word and change the level to 1. It is NOT possible for you to change the level the other way around (from 1 to 2), unless the word was originally level 2.
IMPORTANT: Frequently we get questions from clients that DMC could not transfer data into this or that SQL table. Typically it is a problem of reserved words being used for tables, columns or keys. So when you build your tables keep this in mind and use any technique you prefer so as to avoid this situation. For example, you have a table called PRODUCTS, containing a column named LENGTH. ODBC drivers will be not able to properly open your PRODUCTS table on some versions of SQL, so rename the column to PRD_LENGTH or come to this module and CHANGE the LENGTH reserved word to level 1.
TIP: For Clarion users, you can start the process to port your application to SQL, and DMC will show you all the places where your dictionary is using an SQL Reserved Word as a table, column or key name. Even if you don't plan to convert to SQL right now, it's a good idea to see where you may have a conflict in the future.