The first thing I do when I see a C5 is delete FoxUser.*

You should also be aware that Crystal Report 7 is not certified for Win2K and newer (that includes XP) and you could experience problems.

>We are currently running into an issue with crystal 7 report viewer. It is an OLE control crviewer32.ocx. Several of our clients have been happily running their applications and running their crystal reports from the vfp app for quite awhile, until recently. We have commenced installing an upgrade to our vfp app and several clients, both with and without the new exe, seem to 'suddenly' be experiencing a problem. As usual the error is not entirely reproduceable on our end. I can in fact reproduce the error in dev mode if I run one paticular crystal report enough times in a row, but some of our clients get the error everytime they attempt to run a report. The ever helpful "OLE Exception Error: Exception code C0000005. Ole object may be corrupt." tells me just about nothing.
>
>We have tried checking our ODBC drivers. (not the problem)
>We have tried Reinstalling all of the dlls required by our application. (not the problem)
>We have tried rewriting the application to instantiate the OLE control each time we run a report and then release the object afterward. (no solution)
>We do have some clients who can run the application and crystal reports without problem but apparently there is no commonality between those who do and those who dont have this problem.
>Beside rewriting the software in ASP.net (which is already underway) How can I find a workaround for this issue!?!
>
>It appears there are many Active X and OLE controls that have problems running out of VFP 6.
>
>Most of the problems we have discovered so far are on XP machines (SP1) running our VFP 6 application using crystal 7, with data dictionaries, and the crystal report viewer (crviewer32.ocx), and of course running on a novell network..although we do have the same issue on some Microsoft networks as well..
>
>I can give fairly detailed specifics if anyone has any ideas on how to solve this issue.
>
>Thanks in advance,
>
>Mike