>Thanks Mark... your answe is great.. but it looks like I need to
>try the OOP way first and use a GRID. What do you think?

Well, it really depends on your philosophy and needs. I find grids to be awkward to deal with because the form designer and its associated grid builder seem rather cumbersum. Plus, grids are a bitch to deal with when you need to dynamically rebuild their underlying data source in your code. I've been keeping eye open for a freebie snippet that lets one programmatically create a grid (much like a Browse command would work), and gives the added features of a grid such as more control over methods and events.

The Browse command is extremely powerful... you can do a lot with it, especially if you know it from earlier versions of FP. There are ways to embedd a browse window into forms and pageframes, so the integration with its container is very similar to that of a grid, and you can sculpt their appearance/contents much faster in code than you can a grid. OTOH, you cannot embed controls into a Browse window, you cannot subclass them, etc. But you can throw up a lot of info very quickly and very dynamically in your code.

In general, if my objective is to only display data, then I tend to go with a Browse approach. If I need more control over the UI, then I go with a grid.