Yep,

I am going to use a single page. It solves both problems at once even though it offends my OOP sensibilities ;)

I would love to see your old prototype stuff regardless. I am so new to ASP.NET that I can learn a great deal from any code samples I can find.

Thanks for your help,

Keith Payne

>>
>>The specific situation is that the current page has a button which inserts data into a table. When the user clicks that button, I want to call a sub in page2 that queries the new data and displays it in page2. Page2 contains the dataset and the display controls.
>>
>>In the click event of the button, there is already code to update the table. I'm not sure how to integrate the existing code with the example that you gave.
>>
>>To answer your first question, the sub only touches controls on it's own page.
>>
>>As you can probably tell I am a newcomer to ASP (VFP Convert) and I am still grappling with some of the fundamental aspects of it.
>>
>>One more question which you might know the answer to: Do you know how to get a browser's scrollbar to work in a frameset? The pages are displayed in a frameset but the only scrollbars that I seem to get are inside the frames. The browser does not display a scrollbar for the entire frameset page when it is taller than the browser window.
>>
>>- Keith Payne
>
>Keith,
>I think you may want to consider doing everything in a single page and getting the look of different frames using DIV tags. (You can get auto scroll bars in the div and still have the browser’s main scroll bar)
>
>The difficulty lies in that you cannot send a page to a client browser unless the client browser asked for it.
>Using frames, the only way that I see this could be done would be to do something like having java script in the client side load of the page that does the save. This script would call a for a new src in the target frame that shows the data causing it's page to be recreated on the server.
>You would have to pass a parameter into the page that shows the data (probably a primary key) and refresh your data table based on that.
>
>We have spent a lot of time over here trying to do similar to what you are looking for and
>ultimately we scrapped the concept of using frames. Even worse, we had a lot of lists that made frequent postbacks which would cause a lot of screen flicker so ideally we wanted to keep the refresh areas small.
>I’ll let you know if I find any of the old prototypes I had done with frames. I can’t remember all the syntax and it was a bear to find.