>Hi Cyrus,
>I have never done this. But there was a trick. For what I remember a browse window is a grid that behaves in parts like a window, in other like a grid (even if it is called by a non OOP command)
>
>try (untestet)
>

>SET COLOR OF SCHEME 1 TO GR+/B, RB+/R, G/R+
>DEFINE WINDOW browse2 IN DESKTOP  FROM 1, 1 TO 25, 100 COLOR SCHEME 1
>BROWSE COLOR SCHEME 1 NAME oBrowse_1 WINDOW browse2 
>oBrowse_1.BACKCOLOR = GETCOLOR()
>oBrowse_1.Column1.BACKCOLOR = GETCOLOR()
>*etc
>

There's also the browse ... name oGrid, which is the shorthand for getting an object reference to the grid (which browse command will create with default PEMs anyway). After that, we can do whatever we want with oGrid - set the dynamic properties of its columns, set its colors, bindevents() to any of the grid's events or proeprties... without having to actually design a grid.