...\<App>\Data Acces Layer

This folder contains the generated source code files to access the database. A set of files is generated for each table and each joined table. Iron Speed Designer creates code classes to access your database for each table. All access to the database table goes through these classes regardless of which web page uses the data.

This folder also contains the Table Binding Files (TBF) that contains information about the database schema and other information used by Iron Speed Designer. There is one file for every table used by the application.

Each Record and Table has a corresponding pair of classes: a “base” class and a “customizable” class. The customizable classes are generated only once and it is safe to include custom application logic within them without fear of them being overwritten.

File	Function
Database schema files <TABLE>Table.xml <VIEW>View.xml <QUERY>Query.xml	Database schema files are used by Iron Speed Designer to specify the database schema for the designated table, view or query. <TABLE> is the name of the database table. Example: OrdersTable.xml
Record class files <TABLE>Record.vb <VIEW>Record.vb <QUERY>Record.vb Base<TABLE>Record.vb Base<VIEW>Record.vb Base<QUERY>Record.vb	The Record family of classes corresponds to a record in the database and implements logic to get data from the object and set data into the object. A customizable class is generated for the Record class. Since this class is generated only once, it is safe to include custom application logic within the class without fear of it being overwritten.
Table class files <TABLE>Table.vb <VIEW>View.vb <QUERY>Query.vb Base<TABLE>Table.vb Base<VIEW>View.vb Base<QUERY>Query.vb	The Table family of classes implement logic to retrieve a set of records based on a filter. The developer can specify the filtering criteria or the application user can specify the criteria through user selectable controls. A customizable class is generated for the table, database view, or query. Since this class is generated only once, it is safe to include custom application logic within the class without fear of it being overwritten.
Table Definition class files	The application uses the table schema information of a database table to access, update and delete data from the application’s database tables. The schema information is stored in a class generated by Iron Speed Designer. The class is called <Table>Definition and is created in a file called <Table>Definition.vb. This class is overwritten whenever the table schema information changes as a result of refreshing a database table schema. There is no customizable class created for this class as it does not typically need to be modified by you.
SQL Interface class files	The SQL interface class contains the access code to retrieve data from and save data to the database through the generated stored procedures. The class is called <Table>SqlAccessGen and is created in a file called <Table>SqlAccess.gen.vb. This class is only generated for tables and views, but not for table joins.

File

Function

Database schema files

<TABLE>Table.xml
<VIEW>View.xml
<QUERY>Query.xml

Database schema files are used by Iron Speed Designer to specify the database schema for the designated table, view or query.

<TABLE> is the name of the database table.

Example: OrdersTable.xml

Record class files

<TABLE>Record.vb
<VIEW>Record.vb
<QUERY>Record.vb

Base<TABLE>Record.vb
Base<VIEW>Record.vb
Base<QUERY>Record.vb

The Record family of classes corresponds to a record in the database and implements logic to get data from the object and set data into the object.

A customizable class is generated for the Record class. Since this class is generated only once, it is safe to include custom application logic within the class without fear of it being overwritten.

Table class files

<TABLE>Table.vb
<VIEW>View.vb
<QUERY>Query.vb

Base<TABLE>Table.vb
Base<VIEW>View.vb
Base<QUERY>Query.vb

The Table family of classes implement logic to retrieve a set of records based on a filter. The developer can specify the filtering criteria or the application user can specify the criteria through user selectable controls.

A customizable class is generated for the table, database view, or query. Since this class is generated only once, it is safe to include custom application logic within the class without fear of it being overwritten.

Table Definition class files

The application uses the table schema information of a database table to access, update and delete data from the application’s database tables. The schema information is stored in a class generated by Iron Speed Designer.

The class is called <Table>Definition and is created in a file called <Table>Definition.vb.

This class is overwritten whenever the table schema information changes as a result of refreshing a database table schema. There is no customizable class created for this class as it does not typically need to be modified by you.

SQL Interface class files

The SQL interface class contains the access code to retrieve data from and save data to the database through the generated stored procedures.

The class is called <Table>SqlAccessGen and is created in a file called <Table>SqlAccess.gen.vb.

This class is only generated for tables and views, but not for table joins.

Data model class-related files

The following are database class-related files. A set of six files is generated for each table and each joined table.

File Name	Description
Base<TABLE>Record.vb	The record class named Base<TABLE>Record.
<TABLE>Record.vb	The customizable record class named <TABLE>Record.
Base<TABLE>Table.vb Base<TABLE>View.vb Base<TABLE>Query.vb	Table, view or query class named Base<TABLE>Table.
<TABLE>Table.vb <TABLE>View.vb <TABLE>Query.vb	Table, view or query customizable class named <TABLE>Table.
<TABLE>Definition.vb	The table schema information class named <TABLE>Definition.
<TABLE>SqlAccess.gen.vb	The SQL interface class named <TABLE>SqlAccessGen used to call the generated stored procedures.

Example: An Orders Table

For example, a table called "Orders" will get the following Data Access Layer files generated for it.

Record files

BaseOrdersRecord.vb

OrdersRecord.vb

Table files
BaseOrdersTable.vb
OrdersTable.vb
OrdersSqlAccess.gen.vb
OrdersDefinition.vb