Comments on: Browser Links http://www.dailydoseofexcel.com/archives/2005/02/28/browser-links/ Daily posts of Excel tips…and other stuff Tue, 07 Feb 2012 23:32:04 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Tiavaez http://www.dailydoseofexcel.com/archives/2005/02/28/browser-links/#comment-24458 Tiavaez Thu, 31 May 2007 22:50:00 +0000 http://www.dailydoseofexcel.com/?p=1026#comment-24458 <p>Very interesting site!</p> Very interesting site!

]]> By: Jon Peltier http://www.dailydoseofexcel.com/archives/2005/02/28/browser-links/#comment-10869 Jon Peltier Wed, 13 Apr 2005 16:56:00 +0000 http://www.dailydoseofexcel.com/?p=1026#comment-10869 <p>Peter -</p> <p>You must first set a reference (VB Editor's Tools menu) to the IE object library.</p> <p>- Jon</p> Peter -

You must first set a reference (VB Editor’s Tools menu) to the IE object library.

- Jon

]]> By: Peter http://www.dailydoseofexcel.com/archives/2005/02/28/browser-links/#comment-10868 Peter Wed, 13 Apr 2005 15:12:00 +0000 http://www.dailydoseofexcel.com/?p=1026#comment-10868 <p>When I copy and paste the above code into Excel's VBA editor, it doesn't register as a subroutine that I can actually run. My problem is that:</p> <p>Dim ieApp As InternetExplorer</p> <p>I don't register "InternetExplorer" as a valid type, e.g. String, Long, Single, etc.</p> <p>Can you help?</p> <p>Thanks,</p> <p>- Peter</p> When I copy and paste the above code into Excel’s VBA editor, it doesn’t register as a subroutine that I can actually run. My problem is that:

Dim ieApp As InternetExplorer

I don’t register “InternetExplorer” as a valid type, e.g. String, Long, Single, etc.

Can you help?

Thanks,

- Peter

]]> By: Helen http://www.dailydoseofexcel.com/archives/2005/02/28/browser-links/#comment-9084 Helen Wed, 02 Mar 2005 16:13:00 +0000 http://www.dailydoseofexcel.com/?p=1026#comment-9084 <p>I've got two quite decent workaround for you. :)</p> <p>One is to use early binding for the ieDoc object, which somehow seems to clarify the compiler's mind and remove the confusion between "links" as an element name and as an element type. Add a reference to "Microsoft HTML object library", declare ieDoc As HTMLDocument, and the loop works fine.</p> <p>The other is to loop through all elements and check their typename. This works with both early and late binding.</p> <p>For Each ieElem In ieDoc.body.all<br> If TypeName(ieElem) = "HTMLAnchorElement" Then<br> Debug.Print ieElem.innertext<br> End If<br> Next ieElem</p> I’ve got two quite decent workaround for you. :)

One is to use early binding for the ieDoc object, which somehow seems to clarify the compiler’s mind and remove the confusion between “links” as an element name and as an element type. Add a reference to “Microsoft HTML object library”, declare ieDoc As HTMLDocument, and the loop works fine.

The other is to loop through all elements and check their typename. This works with both early and late binding.

For Each ieElem In ieDoc.body.all
If TypeName(ieElem) = “HTMLAnchorElement” Then
Debug.Print ieElem.innertext
End If
Next ieElem

]]>