Deselecting, or removing, a table from your application removes your ability to use data from that table in any of the components generated by Iron Speed Designer. Deselecting a table removes its property settings in Iron Speed Designer as well as any affected component properties that reference the table.
Deselecting a table does not modify your underlying database; it does not delete the database table schema from your database nor does it delete any data from your database.
Deselecting a table will not change your application (generated source code) until you next build your application. The application building process looks for tables marked as “deselected” and deletes the Data Access Layer for the table. User interface pages are built based on the updated settings. If you deselect a table and you subsequently change you mind, you can select the table again. However, the updates made to the table property settings and component properties will not be recovered.
When you deselect a table, the following happens immediately:
The table property information is deleted.
References to the deselected tables are removed from named queries.
The component property information is deleted.
The table is marked as “deselected” for the subsequent application build process.
When application building begins:
All databases marked for disconnection are removed from your application’s Web.config file.
All of the related stored procedures are removed from the database.
The related generated record class code file is deleted.
The related generated Data Access Layer class files are deleted.
The related customizable class code files are renamed but not deleted.