After getting the automation tips for how to manipulate IE from Excel from
here and Dicks-blog, I've run into a bit of a snag that I hope is just based
on my lack of comprehension.

I'm using this loop to wait for the page to be ready as I saw in some
examples:

Do
DoEvents
tSystem.Sleep 0.8 ' I put this in to try to troubleshoot since delays seem
to help...
Loop Until IeApp.ReadyState = READYSTATE_COMPLETE


The ReadyState property doesn't seem to mean the same thing as I'd hoped.
Sometimes page can be done loading, ReadyState = 4, but not actually ready
for input. In this case when the keystrokes come, they just impact on the
surface of a busy page and are lost from the sequence.


Am I missing a ReadyState subtlety about frames, forms or scripts on a page?
Can anyone advise me on a better property to wait for if what I really want
is to know whether a keystroke or mouseclick will be accepted on a form in a
frame in IE?

Thank you for your attention,
Ryan