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

Creating a Realistic Progress Bar

Written by Eric Smith, Northstar Computer Systems LLC

In most installation routines, you'll see a progress bar that supposedly represents how far along in the process you are. The funny thing is that the installation progress bar always seems to sit on 95% or 98% forever. If you're building one of these for your application, I'd suggest looking at your process realistically to determine approximately how long it's going to take to do each task. If you're creating a database, for instance, each table creation will take approximately the same amount of time. If you have 10 tables, each time you complete a table, you could increment your progress bar by 10%. If you have additional tasks, time how long they take and adjust your timing appropriately. I'd also suggest running the timing on multiple machines so that you get as accurate a timing as possible.

Keywords: [ ASP Performance ]

Publication Date: 10/1/2000