cancel
Showing results for 
Search instead for 
Did you mean: 

Access denied to read-only data source

04-04-2011 3:09 PM
627 views 3 comments
0 Likes
SAP Managed Tags
Subscribe

I am trying to create a report for a client who is using Pervasive (v 10) as their database engine. I am creating the report using Crystal Reports XI Release 2. For this report I have created a stored procedure that creates a temporary table, gathers information from different sources and inserts the desired rows into the temp table. The last command of the procedure is SELECT (field list) FROM <<temp table>>. This procedure runs fine from the Pervasive Control Center.

I then created a report and used the stored procedure as the data source. When I ran the report, I got a message saying that "Access is denied to a read-only data source". I spent some time researching this on line and found that Crystal Reports makes a read-only connection to the database. This causes my procedure to fail when I try to CREATE the temp table OR insert rows.

I found another post that said I could add a key to the registry to cause the connection to be not read only. The entry is:

HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 11.5\Crystal Reports\Database\ODBC]

"AccessMode"=dword:00000000

This fixed the problem on the machine I'm using to develop the reports. So now I move to a user's machine. I add the same key to their registry and run the report. Now I get a message that says: "Failed to open the connection".

Any suggestions?

0 Likes

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Likes

Hi djurden,

Sorry for jumping in here but I have come across a similar situation and am wondering if you have found a solution? I've posted a thread here as well .

However, in that thread I mistakenly posted that I used the registry key 11.5 but it was version 11.0.

Briefly, I received the same Read-only message but I was using a command object, not a stored procedure. Mine works fine in Crystal but it will not run from the viewer on my client's software.

Any ideas are greatly appreciated, TIA rasinc

Former Member
0 Likes

Yes, I have fixed the problem. The client has migrated their database to SQL Server. The stored procedure works fine there.

0 Likes

Hello,

Use ProcessMonitor to look at the registry keys being accessed on each PC and Modules to verify the same runtime versions of CR and Pervasive are the same.

Thank you

Don