>>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,
>Does the C000005 error occurs on every pc you are using this?
>Are you using an app, or exe?
>Can you construct a sample form with menu resulting in this C000005?
>Rgds,
>Koen


Hi Koen,

So far, I have not noticed any pattern of behaviour with this error. Used to be, I only encountered them when executed from a compile EXE. Last week, I was aghast that it happened even during design time (in the VFP IDE environment).

Re constructing a sample form, I would have to attach a lot of stuff here -- the VCXs, MySQL scripts -- and assume you have MySQL installed. Too much of a hassle for you.

Regards
Dennis