Declaring a variable in aspx page and assigning the value in code behing ASP.Net

[aresung]

Developed a web application in ASP.Net (Framework 1.0), in which I have used
public variable

which is defined in the aspx page and in the code behind will have some
calculations and the

assign some value to that variable.

Example:
reports.aspx
------------
<TABLE cellSpacing="2" cellPadding="0" width="700" align="center">
<%=tstrHTML%>
</TABLE>


reports.aspx.vb
---------------

private void displayReports( )
{
tstrHTML = "<tr><td align=left>Firs t Name</td>" & _
"<td align=left>Last Name</td>" & _
"<td align=left>Sala ry</td>"

tstrHTML += "<tr><td align=left>Binn y</td>" & _
"<td align=left>Fede ral</td>" & _
"<td align=left>2300 00</td>"

}

The application was running fine for the last couple of years and all of a
sudden having some

problem.

Can any one of you help me on figuring out this issue.

Thanks

[John Saunders]

Re: Declaring a variable in aspx page and assigning the value in code behing ASP.Net

"aresung" <u47104@uwewrot e in message news:8c0f40bdb6 b12@uwe...

Developed a web application in ASP.Net (Framework 1.0), in which I have
used
public variable

Are you still running .NET 1.0? What service pack?

What version of Windows are you running? What service pack?

Has anything changed recently? Do you use Windows Update or any other
automatic update technology? Have you recently installed any software?
Perhaps IE7?

Do you have any other versions of the .NET Framework on this machine?

It is unusual for someone to still be running such an ancient version of
..NET. Usually, when people are stuck on ancient versions, they are at least
running .NET 1.1. Is there a reason that you haven't at least upgraded to
..NET 1.1? I'm concerned that the unusual action of not upgrading could be
related to the unusual problem of your application suddenly breaking.

Oh, BTW, what is the exact problem you're seeing? Is it an exception? If so,
then please post the entire exception, including any InnerException. You can
do this by surrounding the breaking code in a Try/Catch/End Try block and
then displaying ex.ToString().

--
John Saunders | MVP - Connected System Developer