Well..., if you want some blue-sky type of discussion, some crazy ideas about how to do this reasonably...
Read up on Application Objects. Also look in the help files for IE and Word on the subject of VBA, which will contain discussions of what objects each application object exposes to automation.
I have NO experience in directly mucking about in HTML and I don't know if IE will cooperate, but...
If you could give IE the name of the page you want (and generate the options such as date, province, etc. as part of the URL), you could get the page "up" - at which time you could tell IE to save the page as HTML.
Step two would be to open a Word Application Object, open the HTML, and do a SaveAs to a Word document. (What I'm hoping is that you can get it to convert that HMTL table into a Word table.) Close the HTML version and round-file it. (Kill filespec should do the trick nicely.)
Step three would be to open the saved Word document and use Automation to read the table directly. To do this, you need to know that Word tables are part of the Component Object Model and are well-behaved.
A document is a member of word's Documents collection. You have a shortcut name available, I think CurrentDocument, when you select a given document. A table is a member of a document's Tables collection. You can access it via numbers or create a Table object in VBA and do a Set-class operation. Set myTable=CurrentDocument.Tables(2) or something like that.
Now, within a table, you have a collection of rows. So to get to a particular row you can do myTable.Rows(2). That's the 2nd row because they are one-based, not zero-based. Then finally, each column in a row is actually called a Cell and is part of the Cells collection for that row.
So you could make a reference that looked like
WordObject.Documents(1).Tables(2).Rows(3).Cells(4) to see the 4th column of the third row of the second table of the first document opened through your word application object. Which is the basis for a really simple loop stepping through the rows and cells (columns) via For-loops.
Now, this is a POSSIBLE approach and it depends on the automated down-load through IE and also on the conversion of the HTML to a Word Document. But if IE cooperates and Word cooperates, it is not impossible to do as a monolithic operation.
You might also try this directly to see if there are any tables in the HTML document, in which case you could omit the conversion step... but since I've never worked on inputting an HTML page before, I'm not going to swear what is available.
Now, how do you find out what is possible? Try it. In debug mode, try first to open an IE object so you can browse. Once the object is open, see what it has in it. I.e. in the debug window, examine the object and open the tree diagram that shows its component collections. If you can load the URL, do so and see what becomes available. Now play with that to see if you can do a SaveAs.
Next, if you have the saved HTML, open it in Word and see what it gives you in the way of collections. If there is a tables collection, you can look at the rows collection and then at the cells collection within a row to see what is in each cell. (The .Value property holds the text/string if there is one.)
It is tedious as hell to do this, but the GOOD news is that you learn a lot by peeking "behind the veil" at each step of the way. And when you are done, you have a far better handle on what is or is not possible.
You asked for discussion. I gave you a theoretical discussion because of a lack of experience in the HTML portion. BUT once you get it into Word, that part IS based on experience. So it is not entirely blue-sky.
Good luck.
