|
Command: Databases, Scan All Tables for Changes |
When you change the underlying database tables upon which your application is built, you need to inform Iron Speed Designer of these changes so that Iron Speed Designer generates code matched to your updated table schemas. You can do this using Iron Speed Designer’s refresh feature. Refreshing your database tables allows Iron Speed Designer to rebuild your application using the updated database tables.
The table below shows the database modifications that require refreshing database schemas to your application.
|
|
Adding |
Renaming / Changing |
Deleting |
|
Table |
|
ü |
ü |
|
Primary key |
ü |
ü |
ü |
|
Table fields |
ü |
ü |
ü |
|
Table field type |
|
ü |
|
|
Table field size |
|
ü |
|
|
Default field value |
ü |
ü |
ü |
|
Foreign key relationship |
ü |
ü |
ü |
|
Refreshing a database schema to your application |
|
Select Databases, Scan All Tables for Changes The database is searched for tables that may require refreshing due to changes in the underlying table definitions. Those tables requiring refreshing are marked in orange in the Databases folder in the Application Explorer. |
|
Select Databases, Accept All Changes or Databases, Accept Changes for Selected Table. This performs the actual refreshing of the tables highlighted in the tree. This gives you the opportunity to de-select any tables you do not wish to refresh. The refreshing process is performed and confirmed. Your application will now incorporate the new database changes the next time you build your application. |
If it is likely that a database field was renamed, the Map Field function can be used to identify the old field currently used by Iron Speed Designer and its renamed counterpart in the database schema. By mapping the old field to the new one, you can retain previously entered table and page properties.
If you have previously created pages with the schema, Iron Speed Designer may not automatically change the page to reflect the changes you have made to the database schema. This is because Iron Speed Designer does not know whether you have made changes to the page and would like it a certain way. If Iron Speed Designer were to automatically make the changes, your customizations on the page will be overwritten every time you can scan database for changes.
You will need to change your page, or recreate the page if you want the changes to be reflected on the page. Specifically, the following types of changes may not be reflected:
New Foreign Key relationships
New Primary Keys – fields may still be shown as editable.
If you have not made many changes to the page, simply recreate the page to let Iron Speed Designer choose the best display style for each field. If you have modified the page, double click on each field on the modified pages and change its display type to reflect the changes.
Because Iron Speed Designer is not a database schema-editing tool, you cannot add, edit or delete database tables in Iron Speed Designer.
Iron Speed Designer cannot detect when you’ve renamed your database. To modify your application to use a renamed database, change your database’s name in your application’s Web.config file. This will preserve all the changes you have made to the application as the application is essentially pointing to the same database but with a different name.