NCS Logo - Click for home page Northstar Developer Center
Platforms
All Platforms
.NET Framework (1.x - 4.x)
Active Server Pages
ASP.NET
C#
SQL Server
VB.NET
Visual Basic

Keywords
.NET Data Types
.NET E-mail
.NET Events
.NET Functions
.NET Object Programming
.NET System.Configuration
.NET System.Diagnostics
.NET System.IO
.NET System.Net
.NET System.Net.Sockets
Active Data Objects
ASP Architecture
ASP Black Belt
ASP Built-in Functions
ASP Built-in Objects
ASP Debugging
ASP Performance
ASP Security
ASP Syntax
ASP.NET Authentication
ASP.NET Controls
ASP.NET Data Access
ASP.NET Features
ASP.NET Master Pages
ASP.NET Page Events
ASP.NET Security
ASP.NET ViewState
Atom
Certifications
COM, DCOM, COM+
Data Access
E-Mail
Errors
Exporting Data
HTML Tips
IIS
Object-Oriented Programming
RSS
SQL
Uncategorized ASP Tips
VB API Programming
VB Forms
VB Syntax
XML

Book Support
Visual Basic 6 Bible
ASP Bible
ASP Weekend Crash Course
ASP.NET At Work
Creating Web Services

Building Multi-Page Forms

Written by Eric Smith, Northstar Computer Systems LLC

A reader asked for some advice on multi-page forms, in which a large form (like an insurance application) requires more than one screen of information. As was mentioned in a previous tip, using Session variables eats system resources quite rapidly. For an application like this, I would put some sort of database behind the scenes to capture data from each page. When the user reaches the end of the application, you can tag the user's record with a "Completed" flag so that it can be exported or processed further. Any records that are not marked as completed and where the last update was more than 24 hours can be assumed to be incomplete and can be deleted. You could also allow the user to come back later to finish, in which case you'll need to write a cookie or store some sort of user information with the record in your database for later retrieval.

Keywords: [ ASP Black Belt ]

Publication Date: 11/1/1999, Last Update: 3/24/2010