PBM: MSXML4 typelib constants not recognized in server-side script

[Vince C.]

Hi,

I've created a web application with Visual Interdev and I've added Microsoft
XML, version 4 in project's references. A META tag has been successfully added
in global.asa:

<!--METADATA TYPE="TypeLib" NAME="Microsoft XML, v4.0"
UUID="{F5078F18-C551-11D3-89B9-0000F81FE221}" VERSION="4.0"-->

But when I write the following code in an ASP server-side javascript:

<p>Value: <% = SOMITEM_ELEMENT %></p>

I get a Microsoft VBScript error '800a01f4'. Undefined variable:
'SOMITEM_ELEMEN T'

I don't get such an error with ADO constants (even though I didn't include
ADOJS.inc). Can someone tell me what's wrong?

Thanks in advance,
Vince C.

[Vince C.]

"Chris Hohmann" <no****@thankyo u.com> a écrit dans le message de
news:um******** *****@TK2MSFTNG P11.phx.gbl...

"Vince C." <no**@hotmail.c om> wrote in message .... Remove version.

<!--
METADATA TYPE="TypeLib"
NAME="Microsoft XML, v4.0"
UUID="{F5078F18-C551-11D3-89B9-0000F81FE221}"
-->

HTH

Thanks, Chris. But this has the side-effect to prevent IntelliSense to work. I
can cope with it however as (desire is not irrelevant) I'm *not* a machine ;-).

Vince C.

[Chris Hohmann]

"Vince C." <no**@hotmail.c om> wrote in message
news:eG******** ******@TK2MSFTN GP10.phx.gbl...

"Chris Hohmann" <no****@thankyo u.com> a écrit dans le message de
news:um******** *****@TK2MSFTNG P11.phx.gbl...

"Vince C." <no**@hotmail.c om> wrote in message ...

Remove version.

<!--
METADATA TYPE="TypeLib"
NAME="Microsoft XML, v4.0"
UUID="{F5078F18-C551-11D3-89B9-0000F81FE221}"
-->

HTH

Thanks, Chris. But this has the side-effect to prevent IntelliSense to

work. I can cope with it however as (desire is not irrelevant) I'm *not* a machine ;-).
Vince C.

Note, the following is merely conjecture on my part but...

It sounds like you have a side-by-side install of MSXML 4.0 with prior
versions of MSXML (2.6/3.0) If this is the case, here are two (2) things
you can try:

1. Uninstall all MSXML components and then reinstall them in reverse
order (4.0 then 3.0 then 2.6)

2. Forego the side-by-side install and only install MSXML 4.0

I don't know what the context of your particular situation is so I can't
really say which approach best suits your needs. And as stated above
this is purely conjecture on my part. The above may or may not have any
bearing on the behavior you are encountering. Let me know if there is
anything else I can do to help.

-Chris Hohmann

[Vince C.]

"Chris Hohmann" <no****@thankyo u.com> a écrit dans le message de
news:er******** ******@TK2MSFTN GP09.phx.gbl...
[...]

Note, the following is merely conjecture on my part but...

It sounds like you have a side-by-side install of MSXML 4.0 with prior
versions of MSXML (2.6/3.0) If this is the case, here are two (2) things
you can try:

1. Uninstall all MSXML components and then reinstall them in reverse
order (4.0 then 3.0 then 2.6)

2. Forego the side-by-side install and only install MSXML 4.0

I don't know what the context of your particular situation is so I can't
really say which approach best suits your needs. And as stated above
this is purely conjecture on my part. The above may or may not have any
bearing on the behavior you are encountering. Let me know if there is
anything else I can do to help.

-Chris Hohmann

Well, it's just MSXML4 being installed on a W2K machine. I never though of
removing previous versions since they are built-in. If I remember correctly,
there is a way (MS KB article) to remove MSXML references and re-register them
in any order. But I don't think I'll need that.

It's probably nice to have it on a development machine but not on a production
server. The one thing I was searching was to have the server recognize MSXML
constants. You gave it to me.

Thanks again for your help,
Vince C.