Thanks for the example Walter.
Aside - make sure you start the progress control at 1, not 0.
There are 2 ways for a server to indicate the page is complete. The first is to set a content-length in the header, then when that has arrived you know it's done. The second is to close your connection.
The server you are talking to though uses a third approach. It sets the Transfer-Coding to chunked (usually done with data streaming) and then adds an end-of-stream marker at the end. This is very cunning, and completely allowable. I will adjust the Webclient class to allow for this. The update will only be in the 9.25 update though - but I could send you an interim file. Which build are you currently on?
Aside: It works in NetDemo because that shows you the data, in .Process, as it comes in - it doesn't wait for PageReceived...
Cheers
Bruce