SQL Statement Generation

Specifies where and how to generate your application’s SQL. Iron Speed Designer automatically generates all the SQL statements required for each database-connected form, web page, table, and report in your application, as well as all the database access logic and storage management code. You do not need to know any SQL to build applications in Iron Speed Designer. The generated SQL is based on your database schema and user interface design. A variety of data filters and navigation components provide your end-users with additional viewing and reporting flexibility.

Option	Description
Inline	Build the application using inline SQL statements. The SQL is placed in the Data Access Layer’s generated code. Inline SQL generation, also called “dynamic SQL” is frequently used when your application must connect to a database that does not support stored procedures.
Stored procedures	Build the application’s SQL in database-stored procedures. The stored procedures are automatically loaded into your database. Stored procedures are frequently the best choice when overall performance is important, because stored procedures generally execute faster than inline SQL.

Can’t generate stored procedures in all cases

Iron Speed Designer may not be able to generate stored procedures in all cases, even though you have selected this option. In these cases, Iron Speed Designer will generate inline SQL. For example, Iron Speed Designer cannot generate stored procedures for Microsoft Access databases, a database product which does not support stored procedures. Also, Iron Speed Designer will not generate stored procedures in cases where it detects your database access credentials do not have sufficient permissions to load stored procedures into the database or execute them once there.

Other reasons why Iron Speed Designer can’t generate stored procedures include:

Your database is “read only”. Check your database permissions to see if any setting has changed to make it read-only, which means stored procedures will not be generated.
Your database tables or views are missing primary keys or Virtual Primary Keys. Check if the changes made to your database views render them capable of having stored procedures generated. For example, a view without a Virtual Primary Key cannot have an Update stored procedure generated.
The Stored Procedures option is set to 'true' in the <App Name>.config file.
<add key="GenerateStoredProcedures" value="True" />

Stored procedure owner

Iron Speed Designer generates stored procedures using the user name you provide to log into the database. We recommend you select the final user name you want to use in production. For example, this is frequently ‘dbo’ for Microsoft SQL Server databases.

SQL Statement Generation

Can’t generate stored procedures in all cases

Stored procedure owner

See Also