New in V3.2: New Business Layer Organizes Application Code

A new Business Layer has been added containing the Table and Record classes to make it easier to consolidate your application-specific business logic. (Visual Studio 2005 projects only). Features, Download.

New in V3.2: Section 508 Compliance

Generate web applications that are compliant with Section 508 of the Rehabilitation Act. Specifically, generated applications are compliant with part 1194.22, Web-based Intranet and Internet Information and Applications. Section 508 compliance allows handicapped users to more easily use web applications, a frequent requirement in governmental and corporate applications. (Enterprise Edition feature). Features, Download.

Handling Non-Updateable Views in Iron Speed Designer V3.X

"Iron Speed Designer provides developers with some great properties to facilitate working with views. Virtual primary keys and virtual foreign keys, the ability to select the column you want displayed in place of a foreign key value...these all greatly enable the use of views in an Iron Speed Designer application." Article...

- Michael Weiss, Independent Developer & Iron Speed Customer

Configuring Microsoft SQL Server 2005

In some cases, Microsoft SQL Server 2005 servers may not be displayed in the Database Servers step of the Application Wizard in Iron Speed Designer. When you first install Microsoft SQL Server 2005, it disables TCP/IP for your default instance or your named instance. This behavior is different than with SQL Server 2000 and was done presumably for security reasons. Without the TCP/IP being enabled, Iron Speed Designer cannot see your database server. Iron Speed Designer uses a Windows API function which requests the set of available database servers via TCP/IP. To enable TCP/IP for your SQL Server default instance or named instance, follow the instructions in this Microsoft Knowledge Base article: http://msdn2.microsoft.com/en-us/library/ms177440.aspx.

You may also want to use "(local)" as the database server name for your Microsoft SQL Server 2005 installation if it's on your local machine, in keeping with common practice in earlier versions of Microsoft SQL Server. To do this, run the 'Microsoft SQL Server Management Studio' and connect 'Database Engine' using '(local)' in Server name.