Community
Showing results for 
Search instead for 
Do you mean 
Reply
Accepted Solution

OLEDB Connection String

Employee
Posts: 4
Country: United States

Re: OLEDB Connection String

Please use "Provider=ACTOLEDB2.1;..." or "Provider=ACTOLEDB2;..." (version independent).

 

The issue occurred because there is no AppId ACTOLEDB2.0.

 

Kind regards,

Konstantin

Loyal Listener
Posts: 69
Country: United States

Re: OLEDB Connection String DB_SEC_E_PERMISSIONDENIED

[ Edited ]

I'm getting this error message using the "CurrentACTOLEDB2" property in a custom Dashboard Component.

 

Dim odbConnection AsOleDbConnection = NewOleDbConnection

Dim strodb AsString = ACTFM.CurrentACTOLEDB2

odbConnection.ConnectionString = strodb

odbConnection.Open()

 

It works for one user, but not another?  Both users are ADMINISTRATORS. 

 

The Provider string definitely is "Provider=ACTOLEDB2.1..."

 

This is for Sage ACT! Premium 2013 Version 15.1.108.0, Hot Fix 2

 

I've already tried the suggestion to repair the Db, rebuild the Ole reporting objects, etc.

 

Thanks in advance for any guidance.

 

Mike Fortier

BrainSell Technologies

mfortier@brainsell.net

Bronze Super Contributor
Posts: 1,248
Country: USA

Re: OLEDB Connection String DB_SEC_E_PERMISSIONDENIED

Did you try to run Act! as adminstrator?

-- Jim Durkin

Highlighted
Loyal Listener
Posts: 69
Country: United States

Re: OLEDB Connection String DB_SEC_E_PERMISSIONDENIED

No I didn't.   I'll check that, but  I was looking for a solution that wouldn't require the additional effort for the client for new installs and such. 

 

Thanks.  Appreciate the feedback.

 

Mike Fortier

BrainSell Technologies.