In ASP.NET 2.0, you will be able to accomplish this type of thing using Master Pages: http://msdn2.microsoft.com/library/wtxbf3hh.aspx[^] In ASP.NET 1.1, you can take a couple of approaches. One is to use UserControls (defined in .ascx files), which in this context would be analogous to a web include file. Another approach would be to create your own subclass of the Page class, then base your webforms on the subclass. There are lots of examples of both approaches out there. Here are a few: http://www.xefteri.com/articles/show.cfm?id=20[^] http://authors.aspalliance.com/mamanze/articles/?path=pagetemplate3[^] http://authors.aspalliance.com/wisemonk/view.aspx?id=AN090302-All[^]

Your question belongs in the ASP.NET Forum. It is possible to do this in ASP.NET 2003, but it gets much easier to do in 2005. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

I'm sure there is a way around it, I'm not familiar with it though, it's not considered "best practice". www.msdn.com may help, or maybe you could post a topic based on that.

That is the point, datasets are not ASP.NET (web site technology), they are ADO.NET and belong in the ADO.NET group :) Rocky <>< www.HintsAndTips.com - Now with "Recommendation" postings www.MyQuickPoll.com - Now with Recent Poll List

From your description, is would appear that 99% of the time it takes to come up with the final result is being taken up by the SQL queries themselves. The code to put the final table with the results is nearly nothing. If these queries are static, meaning you always use the same set of queries the same way, then you might want to look into have the SQL Server run a stored procedure that runs all of your queries for you and returns a small table with the results you want. Then, you would only have to write code to handle the returned table of results, bind your datagrid to it, and not worry about dataset.tables("whatever").row(0).Item(0). RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

I am using the "creat auto..." feature.... So I have to predefine the entire datagrid before hand in order to manually manipulate its properties? I was under the impression that after the datagrid was binded to the dataset and created that I could manipulate it from there. Thanks Cav "Nothing is at last sacred, but the integrity of your own mind." "What lies behind us and what lies before us are nothing compared to what lies within us." - Ralph Waldo Emerson

Currently it is one of many files b/c it is created daily. Once the process is set in place, though, we would make it rename the file and move it and the original copy to another folder so that the active working directory would only have that one TMP file. Got any ideas? THanks "Nothing is at last sacred, but the integrity of your own mind." "What lies behind us and what lies before us are nothing compared to what lies within us." - Ralph Waldo Emerson

So if I keep the control to Validate NOT set and the Causes Validation set to true, I will then be able to have a conditional statement saying: If X is chosen from the dropdown Then there HAS to be something in the textbox Else it is OK to have nothing in textbox ? Thanks Cav "Nothing is at last sacred, but the integrity of your own mind." "What lies behind us and what lies before us are nothing compared to what lies within us." - Ralph Waldo Emerson

Al, Thanks... it worked like a charm!! ;) Cheers Cavall "Nothing is at last sacred, but the integrity of your own mind." "What lies behind us and what lies before us are nothing compared to what lies within us." - Ralph Waldo Emerson

No. I am not caching.. I think I figured out what was causing that specific problem.... Thanks for the advice! "Nothing is at last sacred, but the integrity of your own mind." "What lies behind us and what lies before us are nothing compared to what lies within us." - Ralph Waldo Emerson

Marcie, Have a little trouble creating a function to make the connection and configure adapter.. Can you help me out, please? Forgive me, Im a newbie... Public Sub MakeConnection(ByVal sqlSelect As String) Dim strConn As New OleDbConnection("Provider=""MSDAORA.1"";User ID=whatever;Data Source=VQM;Password=whatever") Dim da As New OleDbDataAdapter(sqlSelect, strConn) 'Dim ds As New DataSet strConn.Open() da.Fill(ds, "VENDORDESC") strConn.Close() End Sub My logic was going to be to take in a string as a parameter that would be the sql statment. Then I would populate the public dataset. Then in the Page_Index_Changed (for example) I would call MakeConnection(whatever), which would populate that dataset and then I would bind the datagrid. I could be way off here... If I am not way off... why does the Page_Load and other methods/events in the class not recognize the MakeConnection function as being defined? Also, aside from making the sqlSelect a public variable... how would I use that as to be able to have the Page_Load logic create the sql string and have it also used in the Page_Index_Changed event? Thanks for the help!! cavall "Nothing is at last sacred, but the integrity of your own mind." "What lies behind us and what lies before us are nothing compared to what lies within us." - Ralph Waldo Emerson

i think I figured out what that problem was... wrong fieldname... oops! ;-) Thanks for replying! "Nothing is at last sacred, but the integrity of your own mind." "What lies behind us and what lies before us are nothing compared to what lies within us." - Ralph Waldo Emerson

cavall wrote: I have not used any behind code in this as far as binding the dataset to the datagrid, etc. Have you add mydataadapter.Fill(dataset); in your code-behind? Mazy "Man is different from animals in that he speculates, a high risk activity." - Edward Hoagland