BST Suite of templates supports ODBC/SQL file drivers for the reminder, appointments, bookings, and resources  Files as described in the File Structures Required(Minimum) help segment.

The "required keys" described in this section need to be included in the dictionary so the template can properly construct the ORDER BY and WHERE statements used in Prop:SQL by the templates.

You can Choose to use BST:Prop:SQL or not and substitute calls made by the templates.  This depends what Template Chain and What Back end you are using.  For Example, the ABC Chain and MSSQL do not need to use it at all, and operates very fast just using the Standard templates.

The only difference you will notice in the templates is an additional prompt button "SQL Settings" that becomes enabled if either the reminder/appointment file, booking file, or the resource file has an ODBC/SQL File Driver.

If you have used the dictionary Synchronizer and imported the files from the backend into the Clarion dictionary, you do not need to check the boxes.  The file(table) name and field names will be the same as the ones used in the SQL tables.

If you generated the backend from the dictionary using any of the various 3rd Party tools available, then you may need to check the boxes.

If you have a SQL table names different than the file names used in the dictionary, then you have to check the Use File "Names" so the template has knowlege to use the correct table name in constructing the Prop:SQL statements.

If you are using external field names for the SQL tables that are different than the field names used in the clarion dictionary, you will need to check the Use "External Field Names" so the template has knowlege to use the correct Field names in constructing the Prop:SQL statements.