The problem occurs irregularly. The application (or at least, the part with the problem) consists of a page with a user control containing two other user controls. The user interacts with the page either by clicking on LinkButtons or anchor tags. At times, the application will run through all of the codebehind, but the page will not render in the browser. At other times, the page will render, but only after 10 minutes of sitting. I know that the application has finished working in the background; something is happening that is making the browser think that it is waiting for something. What can I do? ___________________________________________________________________ Ultimate wisdom from the WebMaster: "You know what...I just don't like that."

The setup: (using IE) 1. Application one opens application two in a frame. 2. Application two involves selecting courses from a list. The list includes asp:linkbuttons for adding and dropping courses. 3. Randomly, the browser will show a blank form where Application two should appear. You can see the address in the status bar below, and the green progress bar indicator shows that it is still working. Sometimes, the frame will eventually render after a few minutes. Sometimes, it won't. 4. After this happens, if you hit the Back button, then go foward, the page is there. It is as if it rendered and we couldn't see it. Can the frame be causing us problems? ___________________________________________________________________ Ultimate wisdom from the WebMaster: "You know what...I just don't like that."

Will this work: 1. I set the EnableClientScript=false on the validators 2. I put the following code in the codebehind: If Page.IsValid = False Then Response.Write("window.location.href=""#TOP"";<" & Chr(47) & "script>") 3. I have an anchor tag in the HTML that looks like this: <a href="TOP"></a> 4. I get a javascript error that says this: Invalid pointer What am I doing wrong? ___________________________________________________________________ <i>Ultimate wisdom from the WebMaster</i>: "You know what...I just don't like that."</x-turndown>

Good idea; how then do I scroll to a specific spot on the page? ___________________________________________________________________ Ultimate wisdom from the WebMaster: "You know what...I just don't like that."

1. Page lists courses, each with a link to the course detail 2. User clicks on course detail, shows new page with detail 3. User clicks on "Add course"; after it adds the course it needs to response.redirect back to the list of courses, to the specific area on the page from whence they came I have tried putting an anchor tag on the page like this: I tried the following lines of code: 1. Response.Redirect("mypage.aspx#COURSE123?type=daily&day=2004-10-17") or 2. Response.Redirect("mypage.aspx?type=daily&day=2004-10-17#COURSE123") For #1, my application could not find the "type" query string parameter so did not navigate to the appropriate control on the page. For #2, I got an error because it thought that "#COURSE123" was part of the "day" query string parameter. What am I doing wrong? ___________________________________________________________________ Ultimate wisdom from the WebMaster: "You know what...I just don't like that."

Hey Marcie! Jerry and I are stuck. The situation here continues, although we hope for a solution in the coming months. We have been basically ordered to make our applications (dues, meeting registration) retain the information if the user clicks away. It was quoted as "unacceptable" if the user went halfway through the form, clicked away, and then came back and didn't see their changes right where they had left them. Is there no way to trigger some sort of event back to the server in this case? If there is not, that's fine. As long as we can prove why it can't be done, then hopefully we can inform the powers that be of that fact. ___________________________________________________________________ Ultimate wisdom from the WebMaster: "You know what...I just don't like that."

I need to be able to capture an event that triggers when a user navigates away from the form they're currently using. When they do, I need to be able to take the contents of the controls on the page and save them in Session, so that when they return they see the data they just entered right where they left it. I think the first part is using the window.onUnLoad javascript event. After that, I'm unsure how to proceed. Am I completely on crack here? I am sure that there are at least 7.3 other solutions to this problem. Help!