NT Permisions with OLE/VB6

[Shaft]

As requested I attach a paint document showing error.<br>
<br>
I am using VB6 running on NT4 under a username with administrator privileges. Word is 97-SR2.<br>
<br>
I start VB6, open a new project and place an OLE control on the form.<br>
I then pick Word document as the object to insert into the control. The message "Permission to use object denied" is then displayed.<br>
<br>
This seems to happen to most Microsoft objects that I try to load (perhaps all Office objects). Others like image, which is the Wang viewer, load quite happily.<br>
<br>
Any help gratefully received. One more point is that Microsoft Office is installed on both NT and Windows97 partitions and they share software.<br>
<br>
Andy<br>
<br>

 

[johnk]

We are having a problem which might be related. If so, we could advise the other when the solution is found.<br>
<br>
We create true multi-tier applications using VB6, DCOM and Windows NT 4.0 Server. Our problem is that unless we give users Administrative permission then DCOM cannot work between client and server. Obviously such permission should be withheld from most clients.<br>
<br>
I'll post the solution here when we find it. Would appreciate your doing the same.<br>
<br>
John K

 

[SRG]

One work around might be to submit processes to the schedule service (or any service you write that you could pass requests to) you start the service with admin rights then when it submits the DCOM requests they arrive with admin rights. I know its a goofey work around but just a suggestion. As for shaft if you are logged into a machine with local admin rights under NT there is nothing you shouldn't be able to do. unless you are launching a process under the system authority or something like that.

 

[johnk]

Shaft, I haven't tried this yet and won't for a few days. But it looks like the solution so I'm passing it along.<br>
<br>
Microsoft has published Windows/2000 Distributed Application specifications for app certification. Even some sample code is included for this permissions issue. It involves something called impersonation and is available in NT/Server 4.0.<br>
<br>
Hope this helps. John