>>>Is there some reason not to replace the BROWSE with a Grid?
>>
>>
>>Hi Ed,
>>
>>I try to prevent a grid use. The browse command makes everything what I need with a one code line: it creates a window, it defines the behaviour of cells, keeps the look/size/position of the last time that was used...
>
>OK, but I'd recommend replacing the BROWSE with a Grid - it could be a separate form in a formset, or a page on a pageframe if necessary, and it integrates directly with the Form/FormSet with a minimum of code. Given the capabilities of the Builder for Browses, it should not be overwhelmingly difficult to create.

I've got a form with a grid that I use to simulate a BROWSE window. It's written so that it's read-only (to prevent the user from by-passing a form's data validation routines) and automatically replaces logical fields with check boxes and the grid sizes when the form is resize. About the only drawback that I can think of is that it (currently) doesn't handle either memo or general fields.

If Joao would like, I'll post the code.