>I have been looking into Cursors once. Something went awry so I just resigned :) I'll try to take a look again.
>
>There could be another problem: in Visual FoxPro TextBox and EditBox are not real Windows controls. So I do not expect them always behave.

PMFJI, but I have used the API cursor functions fairly extensively. Past tense, that is. The cursor API calls worked fine up through vfp5 and under Win9x, in general. Then about the time vfp6 came out and my agency moved to NT4, most of the cursor calls quit working. No errors, they simply quit working. Not sure if it was vfp6 or NTFS or the combination, but the result was bad either way. We spent a lot of time testing, and basically the API calls simply stopped firing.

Hence, I quit using the cursor API calls and developed assorted vfp-code workarounds. Don't know if this fits your situation, but it might.