I am tying to register the Windows Script Component as DCOM by adding
remotable=true to the registration element:

<registration
 description="Membership"
 progid="Membership.WSC"
 version="1.00"
 classid="{b99b0540-4df4-11d4-8299-0050da17af8e}"
 remotable=true/>

However, when the remotable flag is set, I get an "Expecting an attribute
value enclosed in quotes" error
and it won't register.  If I use quotes it registers OK, but it isn't
accessible as a DCOM. Should or
shouldn't be quotes? I would think that there shouldn't be?!?

--
Sam

The quotes are required...

Any problems that you may have with accessing the components via DCOM have to with your DCOM
configuration on the remote server side.  I've never tried remote WSCs with *just* DCOM though I
have successfully used WSCs as remote MTS components.  In either scenario (straight DCOM or MTS),
the WSC still needs to be registered on both the client and the server.

--
Michael Harris
MVP Scripting

I am tying to register the Windows Script Component as DCOM by adding
remotable=true to the registration element:

<registration
 description="Membership"
 progid="Membership.WSC"
 version="1.00"
 classid="{b99b0540-4df4-11d4-8299-0050da17af8e}"
 remotable=true/>

However, when the remotable flag is set, I get an "Expecting an attribute
value enclosed in quotes" error
and it won't register.  If I use quotes it registers OK, but it isn't
accessible as a DCOM. Should or
shouldn't be quotes? I would think that there shouldn't be?!?

--
Sam

It's not working.  Is there a resource on the web that talks about creating
DCOM with VB 6 enterprise?
I found something similar in MS Knowledge base (article Q161837) but it is
for VB 5.  Thanks.

with *just* DCOM though I
(straight DCOM or MTS),