Single Instance of Validation Logic

For example, if you have an Add Page and an Edit Page for a Customer table, you can add validation logic to your pages with a simple code customization. But you must repeat the customization for the AddCustomerPage.aspx and EditCustomerPage.aspx pages. In addition, if you use the classes for the table, you might need to write code to add or edit records using CustomerTable and CustomerRecord classes.

Please see the screen below for the location of the Business Layer in the hierarchy:

As shown above, Iron Speed Designer generates the Business Layer for every table. Each table has two classes in the Business Layer, namely the Record Class and the Table Class.

Since you are writing validation logic for Record validation, select the Record Class and then click on the Code Documentation tab on the right panel to display additional detail as shown below:

The documentation shows there are two methods, SavingData and SavedData, which can be overridden before and after the record has been saved.

If you wish to write your validation routine at a single place, you can write it in this section. Unfortunately, at this time, the only way to write code in this section is to use Visual Studio or Notepad outside of Iron Speed Designer.

There are two sections for each class in each table, one with a Base and one without. You will work on the class without the Base, for example: CustomerRecord.vb.

Select the CustomerRecord Events and then select SavingRecord Method.

Then open the files in Microsoft Visual Studio. A new override section, like the one highlighted below, will appear.

You can write your validion logic there:

Jason is so enthusiastic about Iron Speed Designer that he now refuses to create an application without it. He feels all application development is possible using Iron Speed Designer.