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 gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Automation Error in CR 8.5 using OCX

Status
Not open for further replies.

shthiker

Technical User
Dec 14, 2004
2
US
I am having a problem with repeated, random errors when running a CR8.5 reporet from within MS Access 2002. When running reports I randomly get the error "Object invoked has disconnected from its clients". I know i'm still using the OCX which CR has stopped supporting with version 9 but I have not yet been able to convert my code. The code I'm using with Access is:

CrystalReport1.Formulas(1) = "DateHdr= " & mDateHdr
CrystalReport1.ReportFileName = "TransactionListing.Rpt"
CrystalReport1.Action = 1

Prior to this I set some selection formula criteria and header information that I wouldn't think would cause the problem.

I've read some info on sending a record source with the report but I am not doing that. From within Access I create the table which is ultimately used by CR using Access's queries.

Thanks for any help with this.

Carl
 
Thanks. I looked up the article you referred to and updated the file as suggested. Unfortunately, it did not resolve the issue. And, I know the report is not corrupted because if I rerun it after shutting down access, it will generally run. It may even run several times in a row before getting the error again.

Carl
 
I'm having the exact same issues as shthiker (I modified the Crystl32.dep file, but that did not resolve it). The report I'm having this issue with is one that uses 2 ODBC connections within the same report. I'm using the "Reset" method of the VB report control, and the LogonInfo property (of the VB report control) for my ODBC connections, all from within my VB6 application. I'm using Crystal 8.5 for my report development. I can run this perfectly on my old Windows NT machine, but on my new XP machine, I have this problem. Any reports I'm running from my VB app that only uses 1 ODBC connection runs fine (with these I use the Connect property for the ODBC connection). I have compared files between the old machine (that works), and the new XP machine (that doesn't work)and can't determine what the issue is. Any suggestions???
 
I registered the crystl32.ocx required runtime file MFC42.DLL, and this seems to have resolved my issue. Go figure...
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top