I was given 9 reports to place into a SLX menu for the users to run, and I'm having difficulties with 3 of them. 

When run in the client, the user recieves a "Failed to Retrieve data from database" error. 

I checked all the datasource connections, and they were the same.  I now discovered the following are true when they are run outside of Saleslogix Client:

• Reports run using Microsoft OLE DB Provider for SQL Server and Integrated Security


• Reports run using Saleslogix OLE DB Provider and ADMIN userid/password


• Reports fail using Saleslogix OLE DB Provider and Integrated Security

This lead me to believe it was security related, but then I found out...

• Reports fail in SLX Client when logged in as ADMIN user

Any ideas?

Things to verify:

- Before you Add the Report to SalesLogix, make sure that you select the Correct Driver

- Once the Report is inside SalesLogix, SalesLogix will provide the Connection String based on the Current User. It will not use Integrated Security, as SalesLogix doesn't use Integrated Security.

- If the Report runs for Admin, but not for other users, it may be due to the Security Parsing.

For Example, if I log into SalesLogix and run the following query: SELECT * FROM CONTACT, SalesLogix passes that Query As Is to the Database.

However, if I am logged in as a User, SalesLogix will Parse that Statement and modify it to apply security. The Statement will most likely convert to "SELECT * FROM CONTACT_ WHERE ACCESSID_ = 'THEUSERID'

The more tables that are joined into the Statement, the more complex it becomes after Security is applied.

You should use the SLX Profiler and then run the report.

Pay attention to the Error Log and identify those Queries that fail to Parse. More than likely you will be able to see the SQL Statement as Written and the Statement as sent to the Database.

This will help you identify those queries that may be failing, and help you find a Solution.

Raul, Thanks for the response!

Although, I can't seem to find where I would set the Driver in Crystal 11.  I can find it in 8.5, simply by going to Database - Convert Database Driver. 

Any idea?

Looks like I may have found my answer... -> it's done automatically?

Yes, forgot to mention that tidbit.

I want to emphasize something from my original reply:

The fact that it works for Admin, but not for other users typically indicate that the problem relates to the Security Parsing of the SQL Statements.

Do run the SLX Profiler and you will see the Difference, and should be able to catch any errors as well.