Right now I am, from the client-side, calling an asp with a window.open(). The asp called acquires data from SQL Server 7.0 via stored procedure and then changes data on the client document via window.opener.xxxxxxxx.value = whatever.
This technique results in a brief opening of a window and then closing of the window. The user hates it and so do I.
I noticed a Microsoft site does something very similar but without the window.open() function. I have tried capturing their site but since I get only the generated html I can not see what goes on "under the covers" via the actual asp code. Looks like they are using an IFRAME in the process.
Any ideas how they are doing this???
This technique results in a brief opening of a window and then closing of the window. The user hates it and so do I.
I noticed a Microsoft site does something very similar but without the window.open() function. I have tried capturing their site but since I get only the generated html I can not see what goes on "under the covers" via the actual asp code. Looks like they are using an IFRAME in the process.
Any ideas how they are doing this???