Export erroring for over half of options

[earme]

My VB6 application uses the CRViewer for the reports. I'd like it to be able to export, but half of the export options result in an illegal operation. I've tried to replace the dll's, but it the error still happens. Any ideas? Is there a way to supress the items that error?
The options that error are:
Comma Separated Value(CSV)
Data Inteschange Format (DIF)
Lotus 1-2-3 (WK1)
Lotus 1-2-3 (WK2)
Lotus 1-2-3 (WK3)
Text
Tab Separated Values
Tab Separated Text
Record Style (Column spaces)
Record Style (Column no spaces)
Paginated Text

Thanks!
Earme

 

[synapsevampire]

Perhaps this link will help, it's the example apps for VB:

http://support.crystaldecisions.com/fix/samplescr.asp#Sample applications for application developers

It sounds like you have a wrong .dll or a legacy registry setting.

-k

http://www.informeddatadecisions.com

kai@informeddatadecisions.com

 

[earme]

I wasn't clear, I'm sorry. Everything works through my development machine, that has crystal installed. The problem is when I install my vb6 program on another machine (that doesn't have crystal installed). I've included the dll's from my pc, but I still get the illegal operations.

Earme

 

[synapsevampire]

I suspect that either the target PC had some legacy stuff installed that wasn't unregistered (such as a previous craxdrt.dll), or that you have missing or invalid .dll's.

-k

http://www.informeddatadecisions.com

kai@informeddatadecisions.com

 

[bobbittc]

I'm having the exact same problem. In my case, though, I'd installed the application onto a new machine running a clean installation of Windows 2000 Advanced Server. I created a VB6 application and packaged it and installed it with the Packager application - which installed the DLLs located on my development machine (which is a new WinXP machine that never had any prior version of Crystal on it).

The problem then, clearly, isn't old, out-of-date dlls.

It also probably isn't a DLL registration issue - if that was the case I would think that none of the export options would work, instead of the ones Earme lists.

Finally, the fact that my list of broken export options is identical basically confirms that there is some problem that is probably related to the way that crviewer9.dll references those other dlls.