01-28-2019, 03:46 PM
My usual order of operations is to use browser dialog to log in which will give QM access to the site if credentials are needed. Then IntGetFile to grab the page’s HTML. Then use findrx to parse out the link. Then IntGetFile to download the link.
These things can get tricky though, especially if JavaScript is being used for user interaction to interface with server side programming. It might take lots of reverse engineering to get a good link.
Sometimes I have to do what I call the GUI hack where I automate everything in the browser control. This is always my last resort because so many things can go wrong. Mostly timing while pages load. You also end up with Save As, File Exists, etc windows dialogs that need to be automated. Wait for window active is necessary to control timing.
These things can get tricky though, especially if JavaScript is being used for user interaction to interface with server side programming. It might take lots of reverse engineering to get a good link.
Sometimes I have to do what I call the GUI hack where I automate everything in the browser control. This is always my last resort because so many things can go wrong. Mostly timing while pages load. You also end up with Save As, File Exists, etc windows dialogs that need to be automated. Wait for window active is necessary to control timing.