....
I cant get the debugger to run in ie, however it gives an error with outlook
on line 227,please see below:
g_fPreview = dialogArguments.__IE_PrintType == "Preview";
hope this helps.
I think it does. E.g. it probably helps explain why the regsvr32 command helped.
http://www.msdn.microsoft.com/works...preview/reference/objects/dialogarguments.asp
(MSN search for
dialogArguments site:microsoft.com
)
FYI I found out how we can see the source that the line numbers refer to.
Enter in the Address bar: res://shdoclc.dll/preview.dlg
and then use View Source (Alt-V,c)! That opens a Notepad window
in which (in XP) you can set Word Wrap off (uncheck with Alt-o,W)
and set Status Bar on (check with Alt-V,S). Then scroll to line 228
to see the above line.
BTW when I enter that "URL" in the Address bar it causes its own error message
which is clearer than the one you got and confirms the location of the error in the file.
<example>
Line: 228
Char: 1
Error: 'dialogArguments' is undefined
Code: 0
URL: res://shdoclc.dll/preview.dlg
</example>
I have never been clear in the case of embedded scripts if the line number
was relative to the start of the script or relative to the start of the file which
contained it. I guess we are getting pretty clear evidence from these two
error messages that it is the latter.
It sure would be easier to follow this in the debugger though.
One thing I'm surprised at is that there is no specification of which
script language is to be used. I think it has to be Javascript but
wonder what would happen if some users had VBScript as a default
script language (assuming that that could happen.) Perhaps the caller
establishes that. (Mysteries...)
Glad to see you found a solution.
Robert
---
