The code above waits for the element with id to appear accessible on the web page.

'This will wait maxTimeout miliseconds until raising an error or return (Err.Number 0 Or (GetElementById Is Nothing)) And _ If IIf(IsMissing(isBlocking), True, isBlocking) And _ 'id: id of the html element isBlocking: is the code to be blocked until the element is found Public Function GetElementById(id As String, Optional isBlocking As Boolean) See an example function below that will wait until the element is accessible on the web page and only then will it return it. My answer? Wait until the element appears accessible. This workaround, although somewhat useful, in most cases will be unsatisfactory as still does not guarantee that you will actually be able to access a web element or click a button that simply might not be loaded yet due to some JavaScript running in the background.

One way of going around this problem is using arbitrary delays – leveraging Application.OnTime / Application.Wait / Sleep. The problem is, however, that although IE might state that it has fully loaded the web page this in fact does not always have to be the case and some code might generate errors at random lines of code. 'The row below may sometimes raise an error! While (objIE.Busy Or objIE.READYSTATE READYSTATE.READYSTATE_COMPLETE) Most browser automation code out there includes the following lines of code whenever waiting for the Internet Explorer browser control to finish loading or refreshing: Be sure to checkout my VBA Web Scraping Kit which includes a whole worth of VBA scripts for Web Scraping The problem

Excel vba web browser control