Group:  Microsoft Excel ยป microsoft.public.excel.interopoledde
Thread: To use Excel COM interop ...

Geek News

To use Excel COM interop ...
Mark Dickens <mhdickens[ at ]btinternet.com> 1/30/2007 10:39:51 AM
"To use COM interop, you must have administrator or Power User security
permissions"

What exactly does this mean? Surely using the Excel interop DLL doesn't
require such sweeping security permissions?

I'm looking to develop a software solution using Excel interop for a
customer whose users have fairly constrained permissions. I'm not sure
what questions I need to ask to ensure this would be feasible.

Any help would be greatly appreciated.

Thanks

Mark
RE: To use Excel COM interop ...
jam96-BuffaloJoe 3/1/2007 9:36:03 PM
The question you want to ask:

In this 'constrained' environment,
How do I automate a instance of an excel application.

If the user has the ability to open an excel .xls.

You might try and open excel with another method.
Interop.Excel (reference)
dim oExcel as Excel.Application
Dim myWB as Excel.Workbook
dim MyWS as Excel.Worksheet

Use:

oExcel = new Excel.Application
myWB = oExcel.Workbooks.Add(Excel.XLWBATemplate.xlWBATWorksheet)
myWb.Worksheets.Add(,myWB.Workseets(1))
myWS = myWB.Worksheets(1)
myWS.Select()


get your data...

set a reference to your location on the .xls

then set the cells

myWS.Cells(iRow,1) = "Your Data"

oExcel.Visible = true


User's must have a valid Excel Software Registration.

"Mark Dickens" wrote:

[Quoted Text]
> "To use COM interop, you must have administrator or Power User security
> permissions"
>
> What exactly does this mean? Surely using the Excel interop DLL doesn't
> require such sweeping security permissions?
>
> I'm looking to develop a software solution using Excel interop for a
> customer whose users have fairly constrained permissions. I'm not sure
> what questions I need to ask to ensure this would be feasible.
>
> Any help would be greatly appreciated.
>
> Thanks
>
> Mark
>
Re: To use Excel COM interop ...
Mark Dickens <mhdickens[ at ]btinternet.com> 3/21/2007 10:47:51 AM
Thanks for the reply. Suck it & see was the best approach. I was able to
do all that I wanted as a constrained user.

Guess I shouldn't believe such statements in futire

jam96-BuffaloJoe wrote:
[Quoted Text]
> The question you want to ask:
>
> In this 'constrained' environment,
> How do I automate a instance of an excel application.
>
> If the user has the ability to open an excel .xls.
>
> You might try and open excel with another method.
> Interop.Excel (reference)
> dim oExcel as Excel.Application
> Dim myWB as Excel.Workbook
> dim MyWS as Excel.Worksheet
>
> Use:
>
> oExcel = new Excel.Application
> myWB = oExcel.Workbooks.Add(Excel.XLWBATemplate.xlWBATWorksheet)
> myWb.Worksheets.Add(,myWB.Workseets(1))
> myWS = myWB.Worksheets(1)
> myWS.Select()
>
>
> get your data...
>
> set a reference to your location on the .xls
>
> then set the cells
>
> myWS.Cells(iRow,1) = "Your Data"
>
> oExcel.Visible = true
>
>
> User's must have a valid Excel Software Registration.
>
> "Mark Dickens" wrote:
>
>> "To use COM interop, you must have administrator or Power User security
>> permissions"
>>
>> What exactly does this mean? Surely using the Excel interop DLL doesn't
>> require such sweeping security permissions?
>>
>> I'm looking to develop a software solution using Excel interop for a
>> customer whose users have fairly constrained permissions. I'm not sure
>> what questions I need to ask to ensure this would be feasible.
>>
>> Any help would be greatly appreciated.
>>
>> Thanks
>>
>> Mark
>>

Home | Search | Terms | Imprint Contact
Newsgroups Reader - provided by WiredBox.Net