Link to home
Start Free TrialLog in
Avatar of Blaine Roberts
Blaine Roberts

asked on

vb6 custom application calling crystal reports 2008 getting error

This custom application has been running for many years with no issue.  We had our server crater and had to restore from offsite backup.  The restore seemed to work well and the application runs and works but whenever we try and run a crystal report 2008 we get the below error.  we have uninstalled both the crystal report 2008 package and sp as well as the cr runtimes.   but the below error persists.  we are running the reports via vb6 calls/interop and not as external.   we can manually edit the reports and save them in crystal reports and it works but the visual studio visual basic runtime appears to not be registered correctly or is not seeing where to run the reports.   any thoughts or ideas on items to validate would be apprecaited.

This is how the program works
A VB6 program calls a DLL and sends it paramaters, The DLL was created in VB 2005.net using the Microsoft.InteropFormTools and crystal reports 2008 viewer. The VB6 program will send the DLL, Report Name, Database name and some other stuff. The DLL will then send the data to the crystal report viewer which is embedded in the DLL to display the report.

Error-Description.txt

CrystalDecisions.CrystalReports.Engine.LoadSaveReportException: Invalid report file path.
Avatar of Noah
Noah
Flag of Singapore image

Hi there! :)

One alternative is you can try downloading an older (trial) version of crystal. In particular, the trial version CR 2008 has a tool integrated to open your report and search for fields.
Avatar of Blaine Roberts
Blaine Roberts

ASKER

thanks Noah....the crystal report tool itself is working fine...we can open reports and modify and save them.  the issue is running as a call from vb6 into the crystal runtime for visual studio.  It is not finding the right path or registry or something for it.   thanks for the information - any other thoughts are helpful
@Blaine Roberts In that case, please try reinstalling visual studio and configure/integrate everything again.
Have you looked at the code and verified the report path being passed is correct?

Have you recompiled the application after the crash?

You say it is a VB6 application but then you refer to Visual Studio.  I don't recall that VB6 was ever part of Visual Studio (may be bad memory on my part).
ASKER CERTIFIED SOLUTION
Avatar of Ido Millet
Ido Millet
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial