>>>>>Hi,
>>>>>
>>>>>Does your application have a feature where a user can update multiple records at once?
>>>>>If yes, do you then present the data in a grid? Or another approach?
>>>>>
>>>>>TIA
>>>>
>>>>User marks many records in a grid, set up the fields to change and enter data in not-grid PEMs. This will write record by record and let those with a problem marked.
>>>>Normal entry is by record.
>>>>Conflict solution of many records is hell.
>>>>It might work for a set of complete new records - but then user is used to think record by record.
>>>>
>>>>The single one place where I do this is the settings form of Bin2Text - but then this is for a single developer on the VFP IDE.
>>>
>>>Thank you. The challenge for me will be the columns for the fields that in the application are lookups. This makes the entry already validated. So, I will have to have some columns to be the drop-down (lookup). Other fields, which are free-format text, I don't need to worry about. And I agree that the updating multiple records could be a "hell". Another approach is to allow updating only the free-text columns.
>>>But this is what a customer is asking and - probably -willing to pay for.
>>
>>I found that Combobox doesn't really work very well with data entry in a grid (from a user perspective). Instead I make the textbox readonly and place a button next to it, which opens a list of items. Advantage is for longer lists that they can be searchable, and you avoid strange clicking and scrolling, as well as validation issues.
>>Similar for date picker and delete buttons. See attached image how that was implemented.
>
>Nice! We did a similar thing in MaxFrame. You had to make your query include the decoded reason. A custom textbox - called a txtPicklistValid - which was bound to the reason code, acted like a combobox and could summon a UI to select, as you did. I see you added an add new button.
>
>I went farther in that I only use a form with both a navigation grid and data entry controls. That way the same UI that can add/edit/delete reasons is re-used. Security controls who can do what, not the physical features of the UI.

Yes the second approach is also very user friendly, especially when you are dealing with more than a few controls, or when you also have memo text included. I did this in most places at first, and then even combined those two approaches. Some users prefered editing in the list, while others liked to edit below.