G
GW
Hello,
Been using Visual Studio 2005, SQL express 2005 and C# for last two weeks,
coming from 5 years of Dreamweaver, Classic ASP VBScript and MySQL.
Anyway, my first project involves a validated form with 15 fields.
I have the structure as follows:
Default.aspx
form.ascx
formCode.cs
I was wondering the best way to handle the submitted form after data is
saved in my database table. In classic ASP I would normally do a
response.redirect to the Thankyou.asp file with a message indicating the
enquiry has been received.
I was wondering if there is an easy way not to have to create an additional
ASPX file, and simply hide the form.ascx web control and show for example
thankyouResponse.ascx ? Another idea is to use a Label control, and simply
populate it with text after the data has been saved, but I would prefer to
load an ASCX file,as I have need to run quite a complex piece of SQL which
will determine the exact message to display.
Any general ideas appreciated. I must admit to being slightly overwhelmed
at the scope of how different .NET is to classic ASP. The object orientated
versus Inline coding is proving a lot to get my head around.
Cheers,
G.
Been using Visual Studio 2005, SQL express 2005 and C# for last two weeks,
coming from 5 years of Dreamweaver, Classic ASP VBScript and MySQL.
Anyway, my first project involves a validated form with 15 fields.
I have the structure as follows:
Default.aspx
form.ascx
formCode.cs
I was wondering the best way to handle the submitted form after data is
saved in my database table. In classic ASP I would normally do a
response.redirect to the Thankyou.asp file with a message indicating the
enquiry has been received.
I was wondering if there is an easy way not to have to create an additional
ASPX file, and simply hide the form.ascx web control and show for example
thankyouResponse.ascx ? Another idea is to use a Label control, and simply
populate it with text after the data has been saved, but I would prefer to
load an ASCX file,as I have need to run quite a complex piece of SQL which
will determine the exact message to display.
Any general ideas appreciated. I must admit to being slightly overwhelmed
at the scope of how different .NET is to classic ASP. The object orientated
versus Inline coding is proving a lot to get my head around.
Cheers,
G.