>Dragan,
>Sorry to jump in (especially as you now have it re-written and working) but couldn't you add a method to the editbox to update the required information, then from the other form just call that method passing it the new values. That way the update happens in the correct datasession and you can pass the editbox as before.

Tried, but the problem still persisted - the editbox's connection with the controlsource went sour, as soon as I accessed any properties or ran any methods while I was in the called form. Instead of its actual .value and .seltext, I'd see just random strings picked anywhere in memory - usually some Fox keywords, or variable names. I even tried to switch the data session to editbox's parent form before running any of its methods, but that didn't work either.

I don't really have the inclination nor the time to investigate this bug thoroughly, specially while I'm still in VFP7.1, so I'd rather just stay away from passing bound controls as parameters. Maybe I could have tried to unbind the control first? Mmmmm. Maybe next time.