>Will,
>What a whelming message :) I too think grids are 'red headed step child' or 'secret weapon of VFP' - sounds familiar. I myself prefer them for data entry and users love it compared to dummy 'first,next...find' :)

Cetin,
I had to jump in here :). There are too many of those first,next,back forms running around. Those guys sure make VFP interfaces seem clunky! Stateless solutions are best. In many cases (though not all), we use grids (awa Trees and List View) as "navigators" to point to a "record" and (subsequently) populate TextBoxes for editing. Insome cases we edit a grid. I guess our goal is to get the user to the data as quickly and seamlessly as possible.

>If we could have more and more grid addicts maybe we could push fox team to improve them :)
>PS : Fox2x had this exact words 'Browse is one of the most powerfull commands available in foxpro' (they were kind not to say 'is the most'). Grids couldn't take over all the capabilities of a browse but still it's NICE :)

Again - I jump in:) The utility of 'browse' is under rated. We use it to test our record pointer schemes and debug our data transcribers. We must also remind the fox team that "Command Window" is another under-rated feature. I for one am glad that prototyping processes does not require a formal program or form, to echo prospective process output.

>Cetin
>
>>Renoir,
>>
>>I use multiple controls in columns. One control is bound to a non-updateable view (Grid’s RecordSource) and used for user navigation. The data provides the user with information and a key for requerying the business object. The second control is bound to the business object's oData property. Based on the state of the grid (edit or navigate) the currently active row displays the appropriate control. I think the grid object is the best and most under-rated control Visual FoxPro provides for data-entry. I load all my grids from code. The grid designer is like the view designer. They both get you started using the control but neither is close to provide the functionality required to expose the full capabilities of the control. I am not saying the designers are not up-to-stuff because I think they’re great at what they are designed to do - get you started. But once you understand how to manage and control grid, header, column and column control subclasses. How do they say… forget about it.
>>I have found users overwhelmingly prefer grids for both entering and navigating through data.
>>
>>Will
>>
>>>I'm trying to determine why the developer before me was using a Textbox and a Checkbox in the same column of the grid. Much of the code is unfinished so searching for references wasn't successful. What might help is to know why two controls might be needed. I have not used more than one before and wondered if others do and why. Thanks!
>>>
>>>Regards, Renoir