CR8 Export to Excel Access Violation

[mamartin]

When I export a CR8 report to Excel (regardless of version), I receive an access violation error (Dr. Watson). Anybody else have this problem, and if so, what is the solution?

Thanks,

Michael A. Martin

 

[pgtek]

hi
you need to download patch

for your service pack

http://support.crystaldecisions.com/library/kbase/articles/c2013643.asp

cheers

pgtek

 

[mamartin]

pgtek,

the patch references CR 9 and I'm running version 8. Did I miss something? I followed the link anyway, and see there are patches/hotfixes available for multiple versions. I have Crystal Reports Version 8 Developer Edition. Which service pack/hotfix should I download?

Thanks again,

Michael

 

[pgtek]

hi
what service are you running
like windows nt 4 or windows 2000
you have to get the operating system your crystal software runs on

cheers



pgtek

 

[mamartin]

My development workstation is NT 4.0, however, the app will run on NT and W2K workstations. Is that a problem?

Thanks,

Michael

 

[pgtek]

hi
to be sure download the fix for this windows nt 4
also what version of ms office are you running.
that could be your problem also

cheers


pgtek

 

[mamartin]

pgtek,

I'm not exactly sure what: "to be sure download the fix for this windows nt 4" means. Looking at the web page included in your first posting, I do not see anything that references operating system. Can you post the link that has the fix you are referring to?
Our customers run both Office 97 and 2000, and I have experienced the error with both versions.

Thanks,
Michael

 

[pgtek]

hi check this out

http://support.crystaldecisions.com/communityCS/FilesAndUpdates/v6u2fxls.zip.asp

also

http://support.crystaldecisions.com/communityCS/FilesAndUpdates/rdc_web1.exe.asp

cheers



pgtek

 

[mamartin]

pgtek,

I downloaded the patch for the Windows NT 4.0, but it still does not work. The odd thing is that I have other VB/CR apps that export without a problem to Excel. This app that is giving me problems was created this morning by modifying an existing app. I re-created the deployment package for the original app and installed on the same workstation as the problem one. When I export to Excel with the original app, I have no problems. Frankly, I am puzzled.

Thanks again,

Michael

 

[synapsevampire]

Tis puzzling...

Since it's a rework of an existing app, I'd be suspicious that it's trying to do something twice.

-k