crystal reports The instruction at 0x73dd1351 referenced memory at 0x0

[prettitoni]

Has anyone had such a problem? When I try to refresh my crystal report (8.5), I get the Microsoft error "Crystal Reports has encountered a problem and needs to close...." and then I get "The instruction at 0x73dd1351 referenced memory at 0x00000004. The memory could not be read" Can someone shed some light on why I'm getting this program? I created these reports last week and they were fine!

 

[Davest11]

I'm getting the same error message, but when I attempt to open the report. Crystal crashes, then I get this error - the report will not open in v8.5. I've seen on other forums that this is a generic error that doesn't really point to a particular problem.

When I load the file using Crystal v10, the file loads, but I get the error "The saved data will be discarded since one or more formulas failed to compile." I've checked the Business Objects Knowledge Base, but this error doesn't appear there.

Opening the file in v10 doesn't help me, though, as my customer is using v8.5. Any assistance would be greatly appreciated.

Thanks,

-Dave

 

[Turkbear]

Hi,
If you are running CR from a shortcut created when you installed it, check the properties for that shortcut..It probably points to someplace in your Documents and Settings folder
Change it to point directly to your crw32.exe file..

 

[synapsevampire]

It sounds like the report might have been saved in CR 9 or 10, in which case CR 8.5 can't open it.

Or the report may be using a UFL, or something unsupported by your current CR 10 environment, such as a different connectivity and a SQL Expression.

If you're certain that it was not saved in CR 9/10, then you may have a corrupt report, try rolling back to a previous instance of it.

You should be able to right click the report and check teh Properties->Summary->Origin->Date Last SAved to see whether someone has altered it recently.

-k

 

[Davest11]

Thanks for your imput Turkbear and Synapsevampire. I agree, Synapse, that it's probably a corrupted file. As it will at least open in v10, I'm in the process now of updating a previous version with two days worth of modifications.