Crystal Report Viewer throwing Error 429

I am using a Crystal Report Viewer (version 10) in my VB6 application to display a report based on an Access DB stored on a network drive. Everything works fine on my development machine but when I open the vbform that contains the report viewer control on a user machine that does not have VB or crystal installed I get

Runtime error: 429 Activex component can't create object.

I have registered the crviewer.dll file like so:

VB Code:

Shell "regsvr32 /s \\irpserver1\StrategicPlanner\crviewer.dll", vbHide

Runtime 429 still occurs on user machines. Am I forgetting to register something necessary for the user to utilize a crystal report viewer inside my vb app?

Probably yes. Crystal has many dlls and they must all be installed properly.

In your installation folder look for a file called RunTime.hlp, it will indicate which files need to be installed.

If you are using Visual Studio Installer look for a Crystal MSM file.

Has anyone done this with Crystal 10 or a similar version? So far I find that I need to register

VB Code:

Shell "regsvr32 /s \\irpserver1\StrategicPlanner\crviewer.dll", vbHide
Shell "regsvr32 /s \\irpserver1\StrategicPlanner\craxdrt.dll", vbHide

But now my error reads

Runtime error '-2147206429 (80043ae3)':
Invalid TLV record

http://support.businessobjects.com/c...deployment.pdf

Quote:

---

Originally Posted by brucevde

http://support.businessobjects.com/c...deployment.pdf

---

I looked through these articles from BusinessObjects yesterday. It seems that the only proper way of doing this is with an installer which is exactly what I was trying to avoid.

Probably I'm just going to let my application open a new browser window to the web interface of our crystal enterprise server and I'll let users run reports from there. It just would have been cleaner if it could have been in my VB application.

Quote:

---

Originally Posted by ERage

It seems that the only proper way of doing this is with an installer which is exactly what I was trying to avoid.

---

The only proper way to install almost any non-trivial VB project is with an installer.