In certain cases, the application generated by Iron Speed Designer may run more slowly than anticipated. There are several potential reasons for this.
(1) You can turn on application tracing in your generated application's Web.config file to see where time is being taken in your application. See the online help for the Web.config file for instructions on how to enable application tracing. There are also instructions in the application's Web.config file itself.
(2) Sometimes the Display Foreign Key As (DFKA) facility in your generated application takes longer to retrieve all the records than is desired. You can change this behavior in the Display tab of the Page Properties dialog for individual filter controls on your application's web pages. Specifically, you can choose "Populate All Values" or "Populate Only Values in Result Set". Select "Populate All Values" to make your application run faster on a page-by-page basis.
(3) Sometimes if you have too many DFKA's on a page, then you may be better of joining the tables together instead of using the DFKA, because the DFKA facility reads the DFKA value one record at a time instead of using an underlying join. If a filter has 100 values, for example, this causes 100 separate database reads rather than one from a multi-table join.
On a computer running Microsoft Windows NT, Windows 2000, or Windows XP, after you install Service Pack 1 (SP1) for the .NET Framework 1.0, you may experience slower performance when you run applications that were created by using ASP.NET and Visual Studio .NET. There is a Microsoft Knowledge Base article that discusses this topic and suggests a remedy.
http://support.microsoft.com/default.aspx?scid=kb;en-us;324903
We recommend you install Service Pack 2 or later.