VBA Help file not displayed properly

[Ken McLennan]

G'day there again, Gerry,

I made the changes in the Advanced tab as you suggested, but
there's no script debugger appearing. I'm not getting the error message
that I mentioned previously, either. I DID see that the code for
OLEOBJECTS is the culprit, but I don't know where to go from there. I'll
have another search of the web shortly.

I've since found the DOS version of a script debugger, but it was
of little use. (More likely, my lack of knowledge of how it works caused
it to be of little use).

The scripting error returned also. I think it's possible that this
appearance or disappearance of the error message may depend on whether
I'm on-line or not - I see these lines in the script:

<style>@import url(/Office.css);</style>
<link disabled rel="stylesheet" type="text/css" href="/MSOffice.css">

which leads me to believe that there might be 2 different style sheets
for each situation... maybe. I could well be reading that without my
"Thinking Hat" on.

However, the script error cites Line 39, Character 1 as the cause
of the problem as it "Doesn't support this property or method". The code
from there is:

38 <SCRIPT FOR="document" EVENT="onreadystatechange"_
LANGUAGE="JavaScript">
40 alink0.Click();
41 </SCRIPT>

Now, where I go from here is in the laps of the Gods, or will be
guided by the advice I received =)

Thanks very much for your assistance and advice. It's greatly
appreciated.

That is still extant.

 

[Ken McLennan]

G'day there again, Gerry,

I made the changes in the Advanced tab as you suggested, but
there's no script debugger appearing. I'm not getting the error message
that I mentioned previously, either. I DID see that the code for
OLEOBJECTS is the culprit, but I don't know where to go from there. I'll
have another search of the web shortly.

I've since found the DOS version of a script debugger, but it was
of little use. (More likely, my lack of knowledge of how it works caused
it to be of little use).

The scripting error returned also. I think it's possible that this
appearance or disappearance of the error message may depend on whether
I'm on-line or not - I see these lines in the script:

<style>@import url(/Office.css);</style>
<link disabled rel="stylesheet" type="text/css" href="/MSOffice.css">

which leads me to believe that there might be 2 different style sheets
for each situation... maybe. I could well be reading that without my
"Thinking Hat" on.

However, the script error cites Line 39, Character 1 as the cause
of the problem as it "Doesn't support this property or method". The code
from there is:

38 <SCRIPT FOR="document" EVENT="onreadystatechange"_
LANGUAGE="JavaScript">
40 alink0.Click();
41 </SCRIPT>

Now, where I go from here is in the laps of the Gods, or will be
guided by the advice I received =)

Thanks very much for your assistance and advice. It's greatly
appreciated.

That is still extant.

 

[Ken McLennan]

G'day there again, Gerry,

I made the changes in the Advanced tab as you suggested, but
there's no script debugger appearing. I'm not getting the error message
that I mentioned previously, either. I DID see that the code for
OLEOBJECTS is the culprit, but I don't know where to go from there. I'll
have another search of the web shortly.

I've since found the DOS version of a script debugger, but it was
of little use. (More likely, my lack of knowledge of how it works caused
it to be of little use).

The scripting error returned also. I think it's possible that this
appearance or disappearance of the error message may depend on whether
I'm on-line or not - I see these lines in the script:

<style>@import url(/Office.css);</style>
<link disabled rel="stylesheet" type="text/css" href="/MSOffice.css">

which leads me to believe that there might be 2 different style sheets
for each situation... maybe. I could well be reading that without my
"Thinking Hat" on.

However, the script error cites Line 39, Character 1 as the cause
of the problem as it "Doesn't support this property or method". The code
from there is:

38 <SCRIPT FOR="document" EVENT="onreadystatechange"_
LANGUAGE="JavaScript">
40 alink0.Click();
41 </SCRIPT>

Now, where I go from here is in the laps of the Gods, or will be
guided by the advice I received =)

Thanks very much for your assistance and advice. It's greatly
appreciated.

That is still extant.

 

[Ken McLennan]

G'day there again, Gerry,

I made the changes in the Advanced tab as you suggested, but
there's no script debugger appearing. I'm not getting the error message
that I mentioned previously, either. I DID see that the code for
OLEOBJECTS is the culprit, but I don't know where to go from there. I'll
have another search of the web shortly.

I've since found the DOS version of a script debugger, but it was
of little use. (More likely, my lack of knowledge of how it works caused
it to be of little use).

The scripting error returned also. I think it's possible that this
appearance or disappearance of the error message may depend on whether
I'm on-line or not - I see these lines in the script:

<style>@import url(/Office.css);</style>
<link disabled rel="stylesheet" type="text/css" href="/MSOffice.css">

which leads me to believe that there might be 2 different style sheets
for each situation... maybe. I could well be reading that without my
"Thinking Hat" on.

However, the script error cites Line 39, Character 1 as the cause
of the problem as it "Doesn't support this property or method". The code
from there is:

38 <SCRIPT FOR="document" EVENT="onreadystatechange"_
LANGUAGE="JavaScript">
40 alink0.Click();
41 </SCRIPT>

Now, where I go from here is in the laps of the Gods, or will be
guided by the advice I received =)

Thanks very much for your assistance and advice. It's greatly
appreciated.

That is still extant.

 

[Ken McLennan]

G'day there again, Gerry,

I made the changes in the Advanced tab as you suggested, but
there's no script debugger appearing. I'm not getting the error message
that I mentioned previously, either. I DID see that the code for
OLEOBJECTS is the culprit, but I don't know where to go from there. I'll
have another search of the web shortly.

I've since found the DOS version of a script debugger, but it was
of little use. (More likely, my lack of knowledge of how it works caused
it to be of little use).

The scripting error returned also. I think it's possible that this
appearance or disappearance of the error message may depend on whether
I'm on-line or not - I see these lines in the script:

<style>@import url(/Office.css);</style>
<link disabled rel="stylesheet" type="text/css" href="/MSOffice.css">

which leads me to believe that there might be 2 different style sheets
for each situation... maybe. I could well be reading that without my
"Thinking Hat" on.

However, the script error cites Line 39, Character 1 as the cause
of the problem as it "Doesn't support this property or method". The code
from there is:

38 <SCRIPT FOR="document" EVENT="onreadystatechange"_
LANGUAGE="JavaScript">
40 alink0.Click();
41 </SCRIPT>

Now, where I go from here is in the laps of the Gods, or will be
guided by the advice I received =)

Thanks very much for your assistance and advice. It's greatly
appreciated.

That is still extant.

 

[Ken McLennan]

G'day there again, Gerry,

I made the changes in the Advanced tab as you suggested, but
there's no script debugger appearing. I'm not getting the error message
that I mentioned previously, either. I DID see that the code for
OLEOBJECTS is the culprit, but I don't know where to go from there. I'll
have another search of the web shortly.

I've since found the DOS version of a script debugger, but it was
of little use. (More likely, my lack of knowledge of how it works caused
it to be of little use).

The scripting error returned also. I think it's possible that this
appearance or disappearance of the error message may depend on whether
I'm on-line or not - I see these lines in the script:

<style>@import url(/Office.css);</style>
<link disabled rel="stylesheet" type="text/css" href="/MSOffice.css">

which leads me to believe that there might be 2 different style sheets
for each situation... maybe. I could well be reading that without my
"Thinking Hat" on.

However, the script error cites Line 39, Character 1 as the cause
of the problem as it "Doesn't support this property or method". The code
from there is:

38 <SCRIPT FOR="document" EVENT="onreadystatechange"_
LANGUAGE="JavaScript">
40 alink0.Click();
41 </SCRIPT>

Now, where I go from here is in the laps of the Gods, or will be
guided by the advice I received =)

Thanks very much for your assistance and advice. It's greatly
appreciated.

That is still extant.

 

[Ken McLennan]

G'day there again, Gerry,

I made the changes in the Advanced tab as you suggested, but
there's no script debugger appearing. I'm not getting the error message
that I mentioned previously, either. I DID see that the code for
OLEOBJECTS is the culprit, but I don't know where to go from there. I'll
have another search of the web shortly.

I've since found the DOS version of a script debugger, but it was
of little use. (More likely, my lack of knowledge of how it works caused
it to be of little use).

The scripting error returned also. I think it's possible that this
appearance or disappearance of the error message may depend on whether
I'm on-line or not - I see these lines in the script:

<style>@import url(/Office.css);</style>
<link disabled rel="stylesheet" type="text/css" href="/MSOffice.css">

which leads me to believe that there might be 2 different style sheets
for each situation... maybe. I could well be reading that without my
"Thinking Hat" on.

However, the script error cites Line 39, Character 1 as the cause
of the problem as it "Doesn't support this property or method". The code
from there is:

38 <SCRIPT FOR="document" EVENT="onreadystatechange"_
LANGUAGE="JavaScript">
40 alink0.Click();
41 </SCRIPT>

Now, where I go from here is in the laps of the Gods, or will be
guided by the advice I received =)

Thanks very much for your assistance and advice. It's greatly
appreciated.

That is still extant.

 

[Ken McLennan]

G'day there again, Gerry,

I made the changes in the Advanced tab as you suggested, but
there's no script debugger appearing. I'm not getting the error message
that I mentioned previously, either. I DID see that the code for
OLEOBJECTS is the culprit, but I don't know where to go from there. I'll
have another search of the web shortly.

I've since found the DOS version of a script debugger, but it was
of little use. (More likely, my lack of knowledge of how it works caused
it to be of little use).

The scripting error returned also. I think it's possible that this
appearance or disappearance of the error message may depend on whether
I'm on-line or not - I see these lines in the script:

<style>@import url(/Office.css);</style>
<link disabled rel="stylesheet" type="text/css" href="/MSOffice.css">

which leads me to believe that there might be 2 different style sheets
for each situation... maybe. I could well be reading that without my
"Thinking Hat" on.

However, the script error cites Line 39, Character 1 as the cause
of the problem as it "Doesn't support this property or method". The code
from there is:

38 <SCRIPT FOR="document" EVENT="onreadystatechange"_
LANGUAGE="JavaScript">
40 alink0.Click();
41 </SCRIPT>

Now, where I go from here is in the laps of the Gods, or will be
guided by the advice I received =)

Thanks very much for your assistance and advice. It's greatly
appreciated.

That is still extant.

 

[PD.Lees]

Ken,

I see these lines in the script:

<style>@import url(/Office.css);</style>
<link disabled rel="stylesheet" type="text/css" href="/MSOffice.css">

which leads me to believe that there might be 2 different style sheets
for each situation... maybe.

Actually, no, the function of these two lines is simply to link the
help topics to the more suitable version of the cascading style sheet,
depending on the user's version of Internet Explorer (IE). Version 3.0
of IE doesn't understand the <style> tags or "disabled" attribute, so
the MSOffice.css style sheet is used with this version of the browser.
On systems where IE 4.0 or later is installed, the Office.css style
sheet is used instead.

40 alink0.Click();

That's the clue. An ALink (associative link) is an instruction to the
HTML Help ActiveX control to jump to the topic that contains the
specified keyword. That is not happening in your case because the
registry entries for the ActiveX control are broken, and you must
therefore use the solution I described earlier to fix the entries.

 

[PD.Lees]

Ken,

I see these lines in the script:

<style>@import url(/Office.css);</style>
<link disabled rel="stylesheet" type="text/css" href="/MSOffice.css">

which leads me to believe that there might be 2 different style sheets
for each situation... maybe.

Actually, no, the function of these two lines is simply to link the
help topics to the more suitable version of the cascading style sheet,
depending on the user's version of Internet Explorer (IE). Version 3.0
of IE doesn't understand the <style> tags or "disabled" attribute, so
the MSOffice.css style sheet is used with this version of the browser.
On systems where IE 4.0 or later is installed, the Office.css style
sheet is used instead.

40 alink0.Click();

That's the clue. An ALink (associative link) is an instruction to the
HTML Help ActiveX control to jump to the topic that contains the
specified keyword. That is not happening in your case because the
registry entries for the ActiveX control are broken, and you must
therefore use the solution I described earlier to fix the entries.

 

[PD.Lees]

Ken,

I see these lines in the script:

<style>@import url(/Office.css);</style>
<link disabled rel="stylesheet" type="text/css" href="/MSOffice.css">

which leads me to believe that there might be 2 different style sheets
for each situation... maybe.

Actually, no, the function of these two lines is simply to link the
help topics to the more suitable version of the cascading style sheet,
depending on the user's version of Internet Explorer (IE). Version 3.0
of IE doesn't understand the <style> tags or "disabled" attribute, so
the MSOffice.css style sheet is used with this version of the browser.
On systems where IE 4.0 or later is installed, the Office.css style
sheet is used instead.

40 alink0.Click();

That's the clue. An ALink (associative link) is an instruction to the
HTML Help ActiveX control to jump to the topic that contains the
specified keyword. That is not happening in your case because the
registry entries for the ActiveX control are broken, and you must
therefore use the solution I described earlier to fix the entries.

 

[PD.Lees]

Ken,

I see these lines in the script:

<style>@import url(/Office.css);</style>
<link disabled rel="stylesheet" type="text/css" href="/MSOffice.css">

which leads me to believe that there might be 2 different style sheets
for each situation... maybe.

Actually, no, the function of these two lines is simply to link the
help topics to the more suitable version of the cascading style sheet,
depending on the user's version of Internet Explorer (IE). Version 3.0
of IE doesn't understand the <style> tags or "disabled" attribute, so
the MSOffice.css style sheet is used with this version of the browser.
On systems where IE 4.0 or later is installed, the Office.css style
sheet is used instead.

40 alink0.Click();

That's the clue. An ALink (associative link) is an instruction to the
HTML Help ActiveX control to jump to the topic that contains the
specified keyword. That is not happening in your case because the
registry entries for the ActiveX control are broken, and you must
therefore use the solution I described earlier to fix the entries.

 

[PD.Lees]

Ken,

I see these lines in the script:

<style>@import url(/Office.css);</style>
<link disabled rel="stylesheet" type="text/css" href="/MSOffice.css">

which leads me to believe that there might be 2 different style sheets
for each situation... maybe.

Actually, no, the function of these two lines is simply to link the
help topics to the more suitable version of the cascading style sheet,
depending on the user's version of Internet Explorer (IE). Version 3.0
of IE doesn't understand the <style> tags or "disabled" attribute, so
the MSOffice.css style sheet is used with this version of the browser.
On systems where IE 4.0 or later is installed, the Office.css style
sheet is used instead.

40 alink0.Click();

That's the clue. An ALink (associative link) is an instruction to the
HTML Help ActiveX control to jump to the topic that contains the
specified keyword. That is not happening in your case because the
registry entries for the ActiveX control are broken, and you must
therefore use the solution I described earlier to fix the entries.

 

[PD.Lees]

Ken,

I see these lines in the script:

<style>@import url(/Office.css);</style>
<link disabled rel="stylesheet" type="text/css" href="/MSOffice.css">

which leads me to believe that there might be 2 different style sheets
for each situation... maybe.

Actually, no, the function of these two lines is simply to link the
help topics to the more suitable version of the cascading style sheet,
depending on the user's version of Internet Explorer (IE). Version 3.0
of IE doesn't understand the <style> tags or "disabled" attribute, so
the MSOffice.css style sheet is used with this version of the browser.
On systems where IE 4.0 or later is installed, the Office.css style
sheet is used instead.

40 alink0.Click();

That's the clue. An ALink (associative link) is an instruction to the
HTML Help ActiveX control to jump to the topic that contains the
specified keyword. That is not happening in your case because the
registry entries for the ActiveX control are broken, and you must
therefore use the solution I described earlier to fix the entries.

 

[PD.Lees]

Ken,

I see these lines in the script:

<style>@import url(/Office.css);</style>
<link disabled rel="stylesheet" type="text/css" href="/MSOffice.css">

which leads me to believe that there might be 2 different style sheets
for each situation... maybe.

Actually, no, the function of these two lines is simply to link the
help topics to the more suitable version of the cascading style sheet,
depending on the user's version of Internet Explorer (IE). Version 3.0
of IE doesn't understand the <style> tags or "disabled" attribute, so
the MSOffice.css style sheet is used with this version of the browser.
On systems where IE 4.0 or later is installed, the Office.css style
sheet is used instead.

40 alink0.Click();

That's the clue. An ALink (associative link) is an instruction to the
HTML Help ActiveX control to jump to the topic that contains the
specified keyword. That is not happening in your case because the
registry entries for the ActiveX control are broken, and you must
therefore use the solution I described earlier to fix the entries.

 

[PD.Lees]

Ken,

I see these lines in the script:

<style>@import url(/Office.css);</style>
<link disabled rel="stylesheet" type="text/css" href="/MSOffice.css">

which leads me to believe that there might be 2 different style sheets
for each situation... maybe.

Actually, no, the function of these two lines is simply to link the
help topics to the more suitable version of the cascading style sheet,
depending on the user's version of Internet Explorer (IE). Version 3.0
of IE doesn't understand the <style> tags or "disabled" attribute, so
the MSOffice.css style sheet is used with this version of the browser.
On systems where IE 4.0 or later is installed, the Office.css style
sheet is used instead.

40 alink0.Click();

That's the clue. An ALink (associative link) is an instruction to the
HTML Help ActiveX control to jump to the topic that contains the
specified keyword. That is not happening in your case because the
registry entries for the ActiveX control are broken, and you must
therefore use the solution I described earlier to fix the entries.

 

[PD.Lees]

Ken,

I see these lines in the script:

<style>@import url(/Office.css);</style>
<link disabled rel="stylesheet" type="text/css" href="/MSOffice.css">

which leads me to believe that there might be 2 different style sheets
for each situation... maybe.

Actually, no, the function of these two lines is simply to link the
help topics to the more suitable version of the cascading style sheet,
depending on the user's version of Internet Explorer (IE). Version 3.0
of IE doesn't understand the <style> tags or "disabled" attribute, so
the MSOffice.css style sheet is used with this version of the browser.
On systems where IE 4.0 or later is installed, the Office.css style
sheet is used instead.

40 alink0.Click();

That's the clue. An ALink (associative link) is an instruction to the
HTML Help ActiveX control to jump to the topic that contains the
specified keyword. That is not happening in your case because the
registry entries for the ActiveX control are broken, and you must
therefore use the solution I described earlier to fix the entries.

 

[Ken McLennan]

G'day there Pete,

Actually, no, the function of these two lines is simply to link the
help topics to the more suitable version of the cascading style sheet,

I knew it would be something strange!! If it wasn't for Excel I'd
be a permanent Linux user. (I don't understand that OS either, but at

That's the clue. An ALink (associative link) is an instruction to the

Aha!! Perhaps I'm not as thick as I thought I was. I've identified
a clue! Although, even though I found it I didn't know what to do with
it.

registry entries for the ActiveX control are broken, and you must
therefore use the solution I described earlier to fix the entries.

Yes, that's exactly what I did. However, I had to do it about 3
times. In between the 1st & 2nd I installed SP3 for Office, and I got
the last attempt to work by rebooting between the 'unreg' & 'rereg'
phases.

Still, between your expertise & my swearing and cursing it
worked!!! My VBA help is healthy once more and shows the screens I tell
it to.

The swearing and cursing required no skill, but your knowledge was
invaluable. For your assistance, I offer my great & humble thanks.
Without your contribution my computer would have been hurled into the
passing traffic on the roadway out front by now. Thanks very much for
sharing your skills.

Now I'm off to try to write my Excel application for which my
employer *MIGHT* offer thanks and a handshake. If I'm really lucky there
may be a morning tea with coffee & sticky buns =)

Thank you very much once again, your contribution was invaluable.

Good fortune,

 

[Ken McLennan]

G'day there Pete,

Actually, no, the function of these two lines is simply to link the
help topics to the more suitable version of the cascading style sheet,

I knew it would be something strange!! If it wasn't for Excel I'd
be a permanent Linux user. (I don't understand that OS either, but at

That's the clue. An ALink (associative link) is an instruction to the

Aha!! Perhaps I'm not as thick as I thought I was. I've identified
a clue! Although, even though I found it I didn't know what to do with
it.

registry entries for the ActiveX control are broken, and you must
therefore use the solution I described earlier to fix the entries.

Yes, that's exactly what I did. However, I had to do it about 3
times. In between the 1st & 2nd I installed SP3 for Office, and I got
the last attempt to work by rebooting between the 'unreg' & 'rereg'
phases.

Still, between your expertise & my swearing and cursing it
worked!!! My VBA help is healthy once more and shows the screens I tell
it to.

The swearing and cursing required no skill, but your knowledge was
invaluable. For your assistance, I offer my great & humble thanks.
Without your contribution my computer would have been hurled into the
passing traffic on the roadway out front by now. Thanks very much for
sharing your skills.

Now I'm off to try to write my Excel application for which my
employer *MIGHT* offer thanks and a handshake. If I'm really lucky there
may be a morning tea with coffee & sticky buns =)

Thank you very much once again, your contribution was invaluable.

Good fortune,

 

[Ken McLennan]

G'day there Pete,

Actually, no, the function of these two lines is simply to link the
help topics to the more suitable version of the cascading style sheet,

I knew it would be something strange!! If it wasn't for Excel I'd
be a permanent Linux user. (I don't understand that OS either, but at

That's the clue. An ALink (associative link) is an instruction to the

Aha!! Perhaps I'm not as thick as I thought I was. I've identified
a clue! Although, even though I found it I didn't know what to do with
it.

registry entries for the ActiveX control are broken, and you must
therefore use the solution I described earlier to fix the entries.

Yes, that's exactly what I did. However, I had to do it about 3
times. In between the 1st & 2nd I installed SP3 for Office, and I got
the last attempt to work by rebooting between the 'unreg' & 'rereg'
phases.

Still, between your expertise & my swearing and cursing it
worked!!! My VBA help is healthy once more and shows the screens I tell
it to.

The swearing and cursing required no skill, but your knowledge was
invaluable. For your assistance, I offer my great & humble thanks.
Without your contribution my computer would have been hurled into the
passing traffic on the roadway out front by now. Thanks very much for
sharing your skills.

Now I'm off to try to write my Excel application for which my
employer *MIGHT* offer thanks and a handshake. If I'm really lucky there
may be a morning tea with coffee & sticky buns =)

Thank you very much once again, your contribution was invaluable.

Good fortune,