Ok. If done a simple form with textbox myself.

That's great. It looks like it autocreates the var just like a first assignemnd to a var will create it.

It respects form.BINDCONTROLS. If you run the form with BINDCONTROLS false and set it later to true, the var will be created in that very moment.

So for that I've played around with the debugger to trace it. That's tricky. I need to close the form at all (editor as well), clear the breakpoints, set them again and run the form. I can see the var is created in BINDEVENTS = .t.

Strange feature that.

I think it will fail as soon as you have a point in CONTROLSOURCE, it then assumes it's alias.field or object.[object.]property
CONTROLSOURCE can bound to any property, field or variable.

Thank you for pointing that out.


>It seems to be automatically created by Visual FoxPro - I tried renaming the ControlSource to different things, and in every case the preferences were saved.
>
>>Hilmar,
>>
>>some process needs to create the variable.
>>
>>Trace it down:
>>
>>on app start
>>

>>CLEAR ALL
>>DEBUG
>>SUSPEND
>>

>>Now debugger should be open, no variable should exist
>>in watch window add type('aaa') It should show 'U'
>>Click the left border next to TYPE to set a breakpoint
>>run the app. As soon as the variable is created, the debugger should stop.
>>
>>Update:
>>
>>if this creates with the IDE,
>>
>>start vfp.exe with an additional fpw config file, the config should start a prg what itself does the lines above.