Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Crystal 8/9 conflict

Status
Not open for further replies.

MatDavies

Programmer
Feb 22, 2001
243
GB
Hi,

We have an application that uses the crystal ocx (crystl32.ocx) from crystal 8. One of our clients has installed software which uses crystal 9 and this is breaking the ocx. We can still print reports fine, but we were using the functionality of generating a report on the fly from data in a TrueDB Grid. Now we get the error message "Error 20717 : E" useful huh?
this occurs on the "Crystal.Action = 1" method. Has anyone come accross this before? or does anyone have a work around?

regards

Matt

If you can keep your head while those around you are losing theirs, you obviously haven't grasped the seriousness of the situation
 
I found this thread in the Business Objects: Crystal Reports 3 Integrate Forum (forum768):

thread768-477053

The Business Objects: Crystal Reports 3 Integrate Forum deals with using CR in other programming environments, mostly VB.

Hope this helps.

I used to rock and roll every night and party every day. Then it was every other day. Now I'm lucky if I can find 30 minutes a week in which to get funky. - Homer Simpson
 
thanks for that, I was hoping it would come to that, as it will mean a lot of coding for relativly low functionality, it also only affects a few clients at the moment.

Thanks though.

Matt

If you can keep your head while those around you are losing theirs, you obviously haven't grasped the seriousness of the situation
 
as a means of closing this thread, I thought i'd report back on the work around that I have found.

The problem lies in the crpe32.dll, the crystal9 product updated this file, which stopped our product working. By putting the crystal 8.5 version of this file in the same location as our exe it seems to have fixed the problem. I'm assuming that because it is in the local path of the exe it get used instead of the dll in system32.

Hopefully this will help anyone who also comes accross this problem.

Matt

If you can keep your head while those around you are losing theirs, you obviously haven't grasped the seriousness of the situation
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top