Disable crystal reports XI read only state

[Former Member]

We are having errors running crystal reports XI with pervasive v11 (32bit and 64bit).

We receive database connector error and database vendor code: -5099 when running reports that utilize stored procedures. We do not have the errors from crystal when running in pervasive v10.

I have found other people have had this issue with crystal X and resolved it by disabling the crystal reports read only state by altering the registry entries for crystal X (they added a DWORD entry “AccessMode “= 0).

Has anyone done this for crystal XI. If so where did you add it in the registry? We would like to do it in HKEY_Local_Machine .

Thanks,

[former_member183750 · Accepted solution]

You have another identical post to this. Why create this one?

- Ludek

[Former Member · Accepted solution]

Hi Ludek,

i see this as a different subject (but may be a potential solution to my other question). i found some people were able to resolve this issue by disabling the read only state of crystal X. I have not been able to see how to do that in XI and that is really what my question is.

[former_member183750 · Accepted solution]

Could you provide links to where you saw these suggestions?

- Ludek

[Former Member · Accepted solution]

http://cs.pervasive.com/error.htm?aspxerrorpath=/forums/p/13736/47245.aspx

[Former Member · Accepted solution]

is this the correct registry entry?

[HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 11.0\Crystal Reports\Database\ODBC]

add DWORD entry AccessMode

[former_member183750 · Accepted solution]

Well, reading the content on the link you provided, that would be the key for CR 11. I also found this KBA:

1197846 - "Database Connector Error: 'HY000:[Oracle][ODBC][Ora]ORA-01456: May not perform insert/del...

which confirms the reg path.

I still would not discount upgrading to CR XI R2A though...

- Ludek

[Former Member · Accepted solution]

it seems that others have had the same issues running crystal 2008. so i think we would still have the issue with CR XI R2A. can anyone confirm this has been resolved in CR XI R2A?

[Former Member · Accepted solution]

Hi Ludek,

issue 1197846 is also present in CR XI R2A. we have tried the suggested registry setting without any success. Is there a way to find out of this is also an issue for crystal reports 2011 viewer? i have been on a few chat sessions with sales / support and no one seems to know.

[former_member183750 · Accepted solution]

Hello Gary

CR 2011 trial can be downloaded from here:

http://www.sap.com/solutions/sapbusinessobjects/sme/freetrials/index.epx

I do not think CR 2011 will be a solution to the issue though. I discussed this issue with Don, one of my coworkers who used to work a lot with Btrieve and Crystal Reports - when Btrieve was in it's greater days - and I pointed him to the link (http://cs.pervasive.com/forums/p/13736/47245.aspx) you provided. He added a post that you may want to read. Apparently, CR never supported / worked with Stored Procs from Btrieve.

As this is something that was never implemented, it would be considered an enhancement, not a bug. And to get an enhancement added to CR, we need it on the SCN Idea Place. For CR the link would be:

https://ideas.sap.com/ct/s.bix?c={A5E8DEA8-D886-4250-BA2B-039F7D32FFC0}

Now, just to make sure all cards are on the table - face up; Btrieve is a pretty small market, certainly as far as CR / SAP is concerned. E.g.; this year, you are the second person to ask about Btrieve issues. I have heard of one other issue / query. So, implementation of any enhancement for Btrieve will more than likely have a vanishingly small priority. Just being honest...

- Ludek

[former_member11696 · Accepted solution]

I should add something here which may be the reason why it never worked. Crystal requires a cursor to hold the data in when using SP's. I have never tried this or even looked it up actually, but if Pervasive has the ability to use Cursors then it may work in CR Designer.

And the last SELECT Statement is where CR expects the result set to be in. So you may need to dump your data into a temp table in the SP and then CR should be able to report off it.

Also, use ODBC, the Pervasive OLE DB provider simply connects to MS's OLE DB for ODBC so all you are doing is adding another layer on top of ODBC.

Don