Steve -

>With this, there is no form. Just old fpw26 code and a GET stack.

you are wrong - vfp9 running fpw26 code creates a (somewhat different) form behind the scene.
If you have a sufficiently large app to maintain, you can work even through OO interfaces -
which is better IMHO when not only accessing form, but subcontrol props.

>The RETURN n, RETURN -1 idea may be the remedy. Good tip!

>
>>Are you sure there is no form? I'd guess Fox wouldn't reinvent get fields straight on the screen if it could just simulate them with textboxes... so maybe there's a form behind the scenes, just like a browse is actually a grid. Besides, if you create a form, activate it, and then start issuing your GETs, they get created inside that form (with form's fonts - try that).
>>
>>If this manipulation you're doing is happening inside a valid(), then you can simply return the difference between current _curobj and the value you want... say, your current _curobj=4 and you want to jump to object 2 - well, return -2.
>>
>>If it's not called from a valid, your option is to run your gets inside a form. I tried that (and aha! my hunch was correct), and Fox created a pageframe with one page, then a textbox for each get field. You can traverse these textboxes, looking for a given controlsource, to get a reference to your desired textbox (object reference, not number) and setfocus to it.
>>
>>p.s. haven't found how does it get out of that READ... maybe you need to visit the last textbox and then tab out of it?