VBA Help File throws Internet Explorer Script error when I click on a link  
Author Message
MBoonie





PostPosted: Visual Basic for Applications (VBA), VBA Help File throws Internet Explorer Script error when I click on a link Top

Hi. I tried to find this subject in the forum, but wasn't able to locate it, so I'm sorry if this has been answered somewhere...

I have a new dev machine at work with Office 2003 (Office 11), VB6, and .NET Studio. The problem I'm having is that the VBA Help isn't working when i'm developing in Office's VBA editor. The appropriate "context sensitive" page pops up, but the neither the "See also", "Methods", etc hyperlinks, nor the hyperlinks in the text work; I receive an "Internet Explorer Script Error", and the message "An error has occured in the script on this page." and a URL that seems to point to the HTM file (e.g. "mk:@MSITStore:C:\PROGRA~1\COMMON~1\MICROS~1\VBA\VBA6\1033\VbLR6.chm::/html/vadatstring.htm")

I also had this problem on my previous machine where I developed in Office 10 (XP) which also had VB6 and .NET studio.

I can't find this problem documented anywhere on the net! Does anyone know if there's a configuration conflict with .net or VB6

Thanks in advance for any help or guidance.



Microsoft ISV Community Center Forums3  
 
 
duck thing





PostPosted: Visual Basic for Applications (VBA), VBA Help File throws Internet Explorer Script error when I click on a link Top

I can't even get this much information on my machines. If I try to get context-sensitive help on anything that isn't part of the "core" VBA package, I just get a blank screen. No search pane, no history pane, nothing. It's not a big deal; I've been working with VBA/Office integration for years and have enough experience to make sense of the other MSDN resources, but it's still annoying...

Office's VBA editor, I'm inclined to conclude, is basically junk if you're doing anything beyond copying cells from hither and pasting them to thither. I don't mean that as a criticism of Microsoft or of the Office package in general -- VBA just seems like it's good enough for your average macro-recording-and-possibly-tweaking-hacker but completely inadequate for writing real code. I've basically given up on it. I'm currently porting my "old" VBA code to .NET and I'm much happier for it.