In addition to what Walter mentioned, I recently had a similar problem which I eventually traced to a mismatched field type. The report that crashed with the C0000005 error had a field that originally was a datetime type, upon client request I had altered the field to a character and somehow forgot to update this one report. The report would immediately crash with a C0000005 error. Try opening the report in full Crystal Reports, using the actual data that is causing the crash, and see if it doesn't flag a field as unmapped if you do a verify database under the database menu.

Randy

>Chaps
>
>I am trying to run a Crystal report(version 8.0 developers edition) in the Crystal Active X viewer using Foxpro 6 (Service Pack 3). The Crystal report is a report which contains 'On-demand Subreports'. When previewing these subreports and trying to print them i get the following error message and it crashed the machine.
>
>
>Fatal error exception code C0000005
>