Hi Al,

Just thought I'd drop a line to let you know how I got on. Turns out I had a couple ASCAN's built into validation methods which were used frequently. Had a flash of brilliance in the wee hours one morning, and poof! they were replaced by practical code and the gpf's haven't been seen since.

thanks for your help

Sarah


>>I have a reports class and each report is driven by a class based on the reports class.
>>
>>reports has all sorts of good stuff in it which a report might need to know. The report gets driven from a base class method. Infact there's really only one method in a report which needs to be changed and that's the method that drives the queries. Some properties get changed and off we go.
>>
>>So I've successfully used this strategy on a stack of reports but I have one report which just isn't happy. It's gpf'ed along the way so I've had to rewrite queries, simplify etc to coax them through. I've even reinstalled vfp and that got rid of one!
>>
>>Now, I'm left with one I just can't fathom. I run through the method of the class and am about to return control to the calling method which is in the base class. If I use the debugger I can see me leaving the method and the calling method is redisplayed. The little yellow arrow is pointing at the method which has just been run and boom! down it goes. Nothing useful in vfp's error log.
>>
>>I haven't passed any parameters, any data I need has been fed into properties and I get it using "this.xxx". I don't pass any data out. I don't finish my method with "return".
>>
>>How do I trap the reason for this? Any suggestions for next steps?
>
>I had something similar happen to me in VFP5:
>
>http://www.levelextreme.com/wconnect/wc.dll?FournierTransformation~?2,15,349546
>
>I believe in my case it was subtle corruption in a .VCX. IIRC I had to copy the .VCX contents out to a new one (USEing it as a table) then rename appropriately and COMPILE the classlib again.
>
>Before doing that you could manually edit your .VCX and check for bad/extended characters at or near the lines of code causing the problem.
>
>Be sure to back up before hacking your .VCXs!