While it's true, what wOOdy shows there, it's tedious to transform a browse window at runtime, which is what you're doing, if you BROWSE NAME oBrowse NOWAIT and then change the browse window structure via the oBrowse variable. You can do all this with a grid, have it embedded in a form and do all the manipulations visually within the form or class editor and see what you get 1:1
Browse to me is a developer tool to look inside a dbf with a very sparse user interface I wouldn't want to present a user. Data needs to be normalized for data persistence, but users want to see data in a denormlaized natural composition. That is where the data access layer and business logic should always take the steps to turn the data into more natural objects or cursor to display them in forms in grids or listboxes, in several pages of a pageframe, however complex it needs to be.
You can see a browse as a very simple form, but it has a stoneage appeal, it's too tightly coupled to the data. You also won't use the data sheet of Access to view a table or query as a gui frontend.
It's nice, that you can have a hands on the grid, which is inside a browse window. But then, if you like that, you like a grid, then use a grid on a form. You'll likely find something you want to display outside of the list additional to it, like head record data or a summary, even if the form just has an additional border around the grid and a close or edit button on it, it's already much better than a browse.
Bye, Olaf.