>>I see. AFAIK, there are not screens, but DEFINE WINDOW. My manager asked me how to increase the size. First I immediatelly suggested to look at WindowState property, but it later it turned out there are no forms at all. So, we can play with FROM nRow1, nColumn1 TO nRow2, nColumn2 coordinates...
>
>Define Window actually does create a form, with some special set of properties, so it looks that way. Try this:
>

DEFINE WINDOW tt FROM 2,2 TO 45,24
ACTIVATE WINDOW tt
o=_screen.Forms(1)
o.Left = o.Left + 200

This is actually a quite nice way to work with converted apps - I went this way with another monster grown to a few man decades. I added a special control via the @ .... class syntax which gave me OOP-like capabilities for such forms after a analytic phase at start. NOT reccomended for small systems, as the class to add to each screen took more than a few days, but peanuts compared to the number for considered total rewrite.

Today I'ld probably try a similar approach via a companion object using bindevents, but back then vfp6 did its job.

regards

thomas