>>Experience with C5 errors have been varied. I only saw a couple of them. Others saw lots. However, did you notice that you never saw Dr. Watson? The C5 was meant to catch GPFs before Dr. Watson, but with all the problems, Microsoft decided to pull that code out of VFP. What this means is that you'll see Dr. Watson now. However, let me clarify that many of the things that caused the C5 error have been fixed so you shouldn't see Dr. Watson as often as you saw C5.
>
>
>Uhm, what do you mean? Do you mean the intermediate exception handler the MS provided that shows the call stack for your VFP code?
>
>I don't have the final SP3 build but on mine it still pops that info as well
>as capturing some GPFs like those that occur during API calls (some at least).

It may be that the information still pops up. I just installed SP3, but didn't get C5 errors often enough to really tell what it's actually doing now. I'm basing this on information Robert Green presented to the Salt Lake Fox user group last February.