One thing to look for, is a Return within a With-Endwith construct, which can cause a C5 error. http://doughennig.blogspot.no/2006/04/dont-return-inside-with.html

>Hi Koen,
>
>It happens when I fire a form based on a certain frmReport class.
>
>Basically, it contains a 'blank grid'. In the INIT of the form, it creates two CursorAdapter tables, one is a blank empty table which will be the RecordSource, while the other is a table containing metadata of the first table. The metadata has the ff info: field, fieldname, fieldtype. It then uses this info to create the grids columns.
>
>I have used this technique for several years already, but somehow I cant put my finger into the times this BEX problem occurs. It doesn't show any patter of behaviour.
>
>Used to be, this only occurs when the form is fired from the MENU, when I used to fire up the form using the Command result in Menu Builder.
>
>I then read somewhere that forms with grids fired from the Menu must use the Procedure result. Fine, so I changed all forms based on this class to Procedure.
>
>Nowadays, it seems to have been acting up! Even during design time (which NEVER has happened)!
>
>The link you provided gave lead to a 'solution' to change System Property setting under the Data Execution Tab.
>
>I have not tried this yet, for fear that I have to change the settings in ALL the PCs using my app! Not quite elegant if I may say so. =(
>
>Have you encountered this? How did you go about it?
>
>Thanks!
>Dennis
>
>
>
>
>
>>>Hi Experts!
>>>
>>>I have a form class with a grid which sets itself up on the fly using details from a cursoradapter specified in the form.
>>>
>>>I used to encounter this BEX problem when I run the form from a menu using the Command type in the Menu Builder. I read somewhere that this (forms with grid in it) poses a problem when run the VFP menu using Command. So, I used a Procedure instead, then calling the form (DO FORM frmFormWithGrid).
>>>
>>>Right now though, it seems to have gotten worse! Even running the same form from the command prompt generates that BEX problem!
>>>
>>>Thanks in advance for your help!
>>>
>>>This is the full text of the error:
>>>
>>>Problem signature:
>>> Problem Event Name: BEX
>>> Application Name: vfp9.exe
>>> Application Version: 9.0.0.7423
>>> Application Timestamp: 49a31c0c
>>> Fault Module Name: StackHash_e98d
>>> Fault Module Version: 0.0.0.0
>>> Fault Module Timestamp: 00000000
>>> Exception Offset: eefeeefe
>>> Exception Code: c0000005
>>> Exception Data: 00000008
>>> OS Version: 6.1.7601.2.1.0.256.1
>>> Locale ID: 13321
>>> Additional Information 1: e98d
>>> Additional Information 2: e98dfca8bcf81bc1740adb135579ad53
>>> Additional Information 3: 6eab
>>> Additional Information 4: 6eabdd9e0dc94904be3b39a1c0583635
>>>
>>>Dennis
>>
>>Hi,
>>
>>Looking at your error report, it seems to me you have a C000005' error.
>>BEX refers to Buffer Overflow Exception.
>>For more details on BEX, kindly visit http://technet.microsoft.com/en-us/library/cc738483(WS.10).aspx
>>
>>C000005 errors are difficult to cure, mostly they are caused by a lack of memory but other reasons are very well possible.
>>Google fore "C000005 VFP" (without the quotes) and you will get 10'000 plus answers.
>>
>>If you encounter continously this error with your application you will have to review your complete coding from the start.
>>
>>Do you have any idea where / on which point of your application this error is caused?
>>
>>Regards,
>>Koen