It is beyond the scope of BST to provide Training/Support for the developer to understand SQL.

Many excellent books are available on the subject.

An example app in C6 ABC is provided using the FireBird Open Source SuperServer.  A brief synopsis of how the application and Backend were created is included. Another example for the booking templates has been added in C55 ABC.

The BST templates are designed to play nicely with all ODBC/SQL backends, however the developer is responsible for all the design/file requirements needed by both.

The developer is responsible for :

Connection strings, creating ODBC Data Sources, setting up the backend, etc.

creating any necessary views for your backend.

creating triggers, generators, etc for the Autoinc features in your backend needed by the BST templates.

Embeds are provided in various points if you need to add/tweak code for these.

making sure proper keys and file/table names are available in the clarion dictionary for the BST templates to use.

See the File Structures Required (Minimum) section for the keys and tables required by the templates.

It is up to the developer to properly handle Date/Time combined fields, arrays, dimensions, groups, data types, reserved words, and other inconsistencies that are unique to the backends used by the developer.

You have the ability to change the templates to use the file/table "names", and whether to use "external field names" in the template prompts under the SQL Settings button. The basic difference is whether you are importing the backend tables to your application, or generating the backend from your application using various 3rd Party tools that are available.