spock41757
04-14-2011, 05:11 AM
Hi,
My company has a server that does various reports through the company intranet, which I want to automate. The sequence is to login, which takes you to the report selection page, which then takes you to the data selection page. After this, it goes to the server and plots the data in a new IE window.
I can successfully automate everything, except getting the final data. The problem seems to be that the final IE window returns the data through a server script/app without updating the URL. So when I try to access the data through the IE.document.all collection, the IE page elements aren't really accessible as the ie.ReadyState is actually in a READYSTATE_ UNINITIALIZED condition. If I use the URL in the window, and do .Navigate2 <url>, it goes to a READYSTATE_COMPLETE, but gives me the items of a previous window (but the data is still in the window).
Is there a way around this, or can it only be solved by talking to the server administrators?
Thanks,
Mike L.
My company has a server that does various reports through the company intranet, which I want to automate. The sequence is to login, which takes you to the report selection page, which then takes you to the data selection page. After this, it goes to the server and plots the data in a new IE window.
I can successfully automate everything, except getting the final data. The problem seems to be that the final IE window returns the data through a server script/app without updating the URL. So when I try to access the data through the IE.document.all collection, the IE page elements aren't really accessible as the ie.ReadyState is actually in a READYSTATE_ UNINITIALIZED condition. If I use the URL in the window, and do .Navigate2 <url>, it goes to a READYSTATE_COMPLETE, but gives me the items of a previous window (but the data is still in the window).
Is there a way around this, or can it only be solved by talking to the server administrators?
Thanks,
Mike L.