Hi Rick,

Thanks for replying.

>>Set MyComDll = Createobject( "MyComDll.MyComObject" )
>>
>>It barks pretty loud and errors out when I try this. Am I mistaken on this? I was going to try instantiating with the < Object > element like an ocx but haven't gotten to it yet.
>
>I wouldn't do that. You'll get all sorts of security violations when you try.

I'am assuming the "wouldn't do that" is to try to use CreateObject(), or do you mean since it is not an ocx, trying to use the object syntax like an ocx will generate the security violations?

>The object syntax would allow downloading controls/cab files etc for installation, but unless the stuff is signed it'll look horrible in the application.
>
>If it's a VFP object you need the VFP runtimes of course.

It is actually an ATL COM DLL I created in VC++. I used the "Simple Object" object which I'm wondering might be the problem, thinking I needed the "Internet Explorer" object instead. It is an invisible object for obtaining User/Machine info that will be used in an Intranet scenario, so we should be able to have the object already on most users' machines.

Displaying my ignorance, I'm not sure what you mean by "signed".

Bill