I'm a little confused. One year ago I was working with VFP 8 and same version of cabuilder but I don't remember to be having this inconvenience before. Anyway, resetting that code in DE is solving my problem.

Thank you Naomi.




>Yes, this is what builder does :( I even remember reading instructions in VFP Promatrix framework how to make sure to not use the DE builder.
>
>>Hello.
>>
>>I'm using VFP 9 and cabuilder to build my cursor adapter classes from SQL Server express 2008. It works normal and I can CREATEOBJECT by code without any problem, but after using the Form's DE builder to add the cursor adapter class, it automatically includes/contains base code into the CA AutoOpen and Init methods which avoid the CA to be instantiated properly. If I manually reset these methods to use the default class code everything works fine.
>>
>>Am I doing something wrong or is there anything not configured properly?
>>
>>It's strange that DE builder is including code like this into the DE's cursor adapter methods because it's already contained into the base class:
>>
>>AutoOpen Method:
>>
>>*** Setup code: DO NOT REMOVE
>>if not pemstatus(This, '__VFPSetup', 5)
>> This.AddProperty('__VFPSetup', 1)
>> This.Init()
>>endif
>>*** End of Setup code: DO NOT REMOVE
>>
>>
>>
>>
>>Init Method:
>>
>>*** Setup code: DO NOT REMOVE
>>local llReturn
>>do case
>> case not pemstatus(This, '__VFPSetup', 5)
>> This.AddProperty('__VFPSetup', 0)
>> case This.__VFPSetup = 1
>> This.__VFPSetup = 2
>> case This.__VFPSetup = 2
>> This.__VFPSetup = 0
>> return
>>endcase
>>set multilocks on
>>llReturn = dodefault()
>>*** End of Setup code: DO NOT REMOVE
>>
>>*** Setup code: DO NOT REMOVE
>>if This.__VFPSetup = 1
>> This.__VFPSetup = 2
>>endif
>>return llReturn
>>*** End of Setup code: DO NOT REMOVE
>>
>>
>>
>>
>>Thanks
>>
>>Juan C. Jaramillo