>>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.
>
>Hi Dragan,
>I have no dev machine here
>
>is there a difference between
>

BROWSE COLOR SCHEME 1 NAME oBrowse_1 WINDOW browse2

>and
>

BROWSE COLOR SCHEME 1 NAME oGrid

>except the namw of the var and that the window is not defined before BROWSE * ?

In the first case you tell Fox to create a window for the browse with the same PEMs as the browse2 window (and I'm still not sure whether it IS the same window or a copy of it); in the latter case the window is created automatically, with default PEMs. So the first approach gives you more control, as you can define the browse2 window any way you like - pick font, caption etc etc.

Just tried

oFrm=newobject("form")
ofrm.Visible= .T.
BROWSE name oGrd window (ofrm.Name)

and the grid has no parent. The grid is on top of the form, but I can drag it away. If I do

BROWSE name oGrd in window (ofrm.Name)

then still type("ogrd.Parent")="U" but oGrd is hosted in the form, and oFrm.controlcount=0, ofrm.Objects.count=0. Form behaves as an MDI form - if I add another browse grid to the same form, they are both hosted in it. Also, the default size of the grid is just the same fraction of the form's size (in my case, ogrd.height/ofrm.height=076, ogrd.width/ofrm.width=0,745 - same as what I get when I omit the oFrm and browse... name in _screen and check ogrd.width/_screen.width).