I feel so grown up, being able to cure my ills myself :). Yes, passing a string would be no problem, except I needed to pass a selection in it as well - which means .selstart, etc. Passing the editbox sounded so logical... until I hit the datasession wall. Luckily, the speed wasn't too big, just a few bruises :).

BTW, while doing this, I've found that .selstart="some text" is equivalent to this.value=stuff(this.value, this.selstart+1, this.sellength, "some text"). The famous "off by one" where I'd never expect it.

>Yeah, passing a data session bound object between data sessions is probably hazardous to one's health *s*. You'd be a whole lot better off just passing the data itself as a string back and forth. Glad you got it working.
>
>>Now the whole problem here (VFP7.1) is that I'm passing a bound editbox as a parameter, and fiddling with its value in a form which runs in a different datasession - which is giving me trouble. Playing further with this, I noticed that the .text, .seltext, .value also had strange values when seen from the code in the called form. Somehow the bound control loses conection with its controlsource when its source-related properties are accessed (or assigned) in a different datasession. Don't know if this still holds in VFP8 - and I don't remember this mentioned anywhere as a bug.
>>
>>The solution was simple: