References to ado210.chm keep popping up since yesterday... can't shake it.

[MLH]

I registered an ocx control written by a colleague then ported
his A2000 app backwards to A97. The A2000 app utilzed ADO,
which I have never before used.

Don't know or when, but it seems to be associated with my use
of A97 HELP now - I keep getting references to a missing ado210.chm
file. I've never gotten this before. I'm afraid that I must have done
something wrong. I use Office 97 Pro edition and the 97 ODE tools.
Am I even supposed to have this file. If not, what can I do to rid
myself of these references to it?

[MLH]

Will try to correct horrific grammatical errors...

I registered an ocx control written by a colleague, then ported
his A2000 app backwards to A97. The A2000 app utilzed ADO,
which I have never before used.

Don't know how or when, but it seems to be associated with my use
of A97 HELP. Now - I keep getting references to a missing ado210.chm
file. I've never gotten this before. I'm afraid that I must have done
something wrong. I use Office 97 Pro edition and the 97 ODE tools.
Am I even supposed to have this file? If not, what can I do to rid
myself of these references to it?

[MLH]

Upon Googling, most of what I find indicates to me that
ado210.chm is something specific to office 2000. I don't
think I should even be seeing references to the file. Could
it be that the OCX control I copied and registered is where
the issue lies?

[Randy Harris]

ado210.chm is the ADO help file. I don't know whether it was supposed to be
part of A97 or not. My guess is that it is the OCX control you loaded that
has a reference to ADO. I'd further guess that you can silence the messages
by simply copying the file into place. If you can't find a copy, I can email
one to you.

Randy
"MLH" <CR**@NorthState.net> wrote in message
news:hg********************************@4ax.com...

Upon Googling, most of what I find indicates to me that
ado210.chm is something specific to office 2000. I don't
think I should even be seeing references to the file. Could
it be that the OCX control I copied and registered is where
the issue lies?