Could you please post exact code you were trying to insert?

Yeah, sure.
Here is the C# code:

<%
protected void ExportTextFile(object sender, EventArgs e)
{
string UserId=System.Environment.UserName;

string constr = ConfigurationManager.ConnectionStrings["constr"].ConnectionString;
using (SqlConnection con = new SqlConnection(constr))
{
using (SqlCommand cmd = new SqlCommand("SELECT @DateCreated AND @NoteContent FROM SnNote"))
{
using (SqlDataAdapter sda = new SqlDataAdapter())
{
cmd.Parameters.Add("@UserId", UserId);
cmd.Connection = con;
sda.SelectCommand = cmd;
using (DataTable dt = new DataTable())
{
sda.Fill(dt);

//Build the Text file data.
string txt = string.Empty;

foreach (DataColumn column in dt.Columns)
{
//Add the Header row for Text file.
txt += column.ColumnName + "\t\t";
}

//Add new line.
txt += "\r\n";

foreach (DataRow row in dt.Rows)
{
foreach (DataColumn column in dt.Columns)
{
//Add the Data rows.
txt += row[column.ColumnName].ToString() + "\t\t";
}

//Add new line.
txt += "\r\n";
}

//Download the Text file.
Response.Clear();
Response.Buffer = true;
Response.AddHeader("content-disposition", "attachment;filename=SqlExport.txt");
Response.Charset = "";
Response.ContentType = "application/text";
Response.Output.Write(txt);
Response.Flush();
Response.End();
}
}
}
}
}%>

I am using this to call it:
<a href="#" runat="server" onclick="<% ExportTextFile();%>" style="height:7px;width:40px;border:outset">PK</a>

Thanks.

For a start, you have a method that is not placed inside a class, and that is what the original error says - you cannot have standalone methods in C#. Other than that, you should really use a codebehind file for your code instead of putting the code inline - see http://www.codeproject.com/Articles/8178/Inline-Single-File-vs-CodeBehind for more details.

Hi all,
you CAN embed methods, but using runat="server" in a script block

see
http://www.808.dk/?code-aspnet-inline
and
http://msdn.microsoft.com/en-us/library/ms178135%28v=vs.100%29.aspx

for examples

I agree that you can do it (but not with old ASP style <% %> tags, but with script runat="server" like you suggest), however I am saying that much better practice is to use the codebehind approach.