Citadel 5 Remote ODBC Permissions

[skibum019]

I am using the CitadelRemoteODBC DCOM configuration to provide ADO access to our Citadel 5 databases through Excel.  I have various spreadsheets that works as long as an administrator is logged into the machine running the Excel spreadsheet.  Other users get no data returned or a permissions error (depending on the coding for that specific sheet).  Anybody have any clues why?

[Ryan.S]

Usually I create the ODBC DSN in Control Panel->Administrative Tools->Data Sources on remote computer, then follow this KB to query the data in Excel.

http://zone.ni.com/devzone/cda/tut/p/id/2970

I don't have much idea of the "CitadelRemoteODBC DCOM". I don't find it in my DCOM configuration. How do you configure the ADO access through Excel?

[skibum019]

Ryan, See: Citadel 5 Remote Database Access Using COM+ and ADO

This is a kb article describing how to access Citadel 5 using ADO.

[skibum019 · Accepted solution]

I think I answered my own question, although I do not know if this is the best way to handle this or not....

On the server where the Citadel database resides, go to the Component Services administration, Right click on "My Computer" and click properties.  Go to the COM Security tab.  As a gross reality check, I made changes to all 4 items, I have not yet tested if limiting 1 or more of these or the associated options will still allow the access....

Access Permissions:

  Edit Limits:  Add the domain user or group an make sure the box is checked to "Allow" for both Local and Remote Access

  Edit Default:  Add the domain user or group an make sure the box is checked to "Allow" for both Local and Remote Access

Launch and Activate Permissions: 

  Edit Limits:  Add the domain user or group an make sure the box is checked to "Allow" for Local Launch, Remote Launch, Local Activation, and Remote Activation

  Edit Default:  Add the domain user or group an make sure the box is checked to "Allow" for Local Launch, Remote Launch, Local Activation, and Remote Activation

Once these changes were made, all users within the domain group I had defined were able to run the ado query.