sql server programming: hello -- I'm trying to help a colleague enhance a dynamic Web-based
query tool. The query hits a database with records of disease
reports. Each record has county, race, age, disease, date of report,
etc. Currently, after running a query, the user always has to start
from scratch to build a new query. I've asked him to create a "Modify
existing search criteria" button so that I don't have to make all of
the same selections if I just want to tweak the query criteria.

For instance, I want to look at disease counts for a particular month,
then I want to press the "modify" button to return to the Select
Criteria page with all of the same criteria still selected so that I
can then select a different month. (eg. When you hit "modify search"
on Travelocity.com. Site does not force you to re-enter departure/
arrival city, etc..)

I feel like this is an easy request, but I am a .net / SQL novice and
my colleague has said it would cause performance hits on the
application and that it would take too long to build to be worth it..
He says it would require him to set up extensive user profiles, etc..
Thoughts?

They're using:
Database is MS/SQL
Microsoft Visual Studio.NET 7.0
Visual Basic 7.0
JavaScript

JB

You'd be better off in a different forum for this type of question - eg the
ASP.NET one. FWIW there are several options eg you could use session
variables or the querystring to pass info from one page to another. Have a
look at "maintaining state" in any ASP/ASP.NET book eg in ASP.NET you can
even maintain state in the SQL Server database to make it accessible across a
webfarm. Once on the second page (or another instance of the initial page)
you read the variables and send them in as parameters to the command object
as per normal.
Cheers,