ASP.NET 2.0 Project - Design Issue?

[dm1608]

Hi -

I have a few Classic ASP projects that I would like to convert to ASP.NET
2.0. I've been learning ASP.NET 2.0 for the past few months.

One of the ASP projects that I'm converting is a simple HTML form that
allows the user to select a few options for a query. Based on their input,
I would dynamically build a SQL query to perform a search based on their
information. I.E., I may have a listbox that allows them to find a text
string for today, last 3 days, last week, last month, or all.

Anyway, after they select their information and hit submit, I then run the
query and create a new page listing the results. It is essentially like a
datagrid listing.

I've been wondering how I can accomplish this same task with ASP.NET 2.0. I
would like to us Data Binding if possible.

One of my challenges is how to have a "Query Form" and a "Results" form. Do
I need two pages or should I simply use the same page for both?

If I use the same page, how do I hide the datagrid until they select a query
option. If they need to run the query again, I want them to click a "Home"
link or soemthing to go back to just the query form.

It would seem most of the GridView examples I've seen online and via
Micosoft webcasts and just too simple to be used in real-world scenarios. I
know most of the time they're simply demonstrating the functionality, but I
seriously cannot see any websites actually implementing the forms and junk
the way they present.

Any insight or examples to this would be appreciated.

[Peter Bromberg [C# MVP]]

You can use the same page, just check for IsPostBack in order to know that
your grid needs to be bound.
You can also put the input controls in a panel and set its visibility on /
off.

Also, you will be a lot better off using stored procedures with input
parameters and
CASE --WHEN statments for the where clause.
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"dm1608" wrote:

Hi -

I have a few Classic ASP projects that I would like to convert to ASP.NET
2.0. I've been learning ASP.NET 2.0 for the past few months.

One of the ASP projects that I'm converting is a simple HTML form that
allows the user to select a few options for a query. Based on their input,
I would dynamically build a SQL query to perform a search based on their
information. I.E., I may have a listbox that allows them to find a text
string for today, last 3 days, last week, last month, or all.

Anyway, after they select their information and hit submit, I then run the
query and create a new page listing the results. It is essentially like a
datagrid listing.

I've been wondering how I can accomplish this same task with ASP.NET 2.0. I
would like to us Data Binding if possible.

One of my challenges is how to have a "Query Form" and a "Results" form. Do
I need two pages or should I simply use the same page for both?

If I use the same page, how do I hide the datagrid until they select a query
option. If they need to run the query again, I want them to click a "Home"
link or soemthing to go back to just the query form.

It would seem most of the GridView examples I've seen online and via
Micosoft webcasts and just too simple to be used in real-world scenarios. I
know most of the time they're simply demonstrating the functionality, but I
seriously cannot see any websites actually implementing the forms and junk
the way they present.

Any insight or examples to this would be appreciated.

[dm1608]

Thanks for the feedback.

Do you have a sample of how to do this? I mean, with a simple form that
prompts for username, password, and perhaps a listbox where its values will
be for the where date range.

I'm familiar with a SP and can create one for this.

I'm just uncertain about the form and datagrid results on same page and how
to bind via code.


"Peter Bromberg [C# MVP]" <pb*******@yahoo.nospammin.com> wrote in message
news:12**********************************@microsof t.com...

You can use the same page, just check for IsPostBack in order to know that
your grid needs to be bound.
You can also put the input controls in a panel and set its visibility on /
off.

Also, you will be a lot better off using stored procedures with input
parameters and
CASE --WHEN statments for the where clause.
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"dm1608" wrote:

Hi -

I have a few Classic ASP projects that I would like to convert to ASP.NET
2.0. I've been learning ASP.NET 2.0 for the past few months.

One of the ASP projects that I'm converting is a simple HTML form that
allows the user to select a few options for a query. Based on their
input,
I would dynamically build a SQL query to perform a search based on their
information. I.E., I may have a listbox that allows them to find a text
string for today, last 3 days, last week, last month, or all.

Anyway, after they select their information and hit submit, I then run
the
query and create a new page listing the results. It is essentially like
a
datagrid listing.

I've been wondering how I can accomplish this same task with ASP.NET 2.0.
I
would like to us Data Binding if possible.

One of my challenges is how to have a "Query Form" and a "Results" form.
Do
I need two pages or should I simply use the same page for both?

If I use the same page, how do I hide the datagrid until they select a
query
option. If they need to run the query again, I want them to click a
"Home"
link or soemthing to go back to just the query form.

It would seem most of the GridView examples I've seen online and via
Micosoft webcasts and just too simple to be used in real-world scenarios.
I
know most of the time they're simply demonstrating the functionality, but
I
seriously cannot see any websites actually implementing the forms and
junk
the way they present.

Any insight or examples to this would be appreciated.