>>>>Is there a method on
>>>>the form or in the grid, to perform tableupdate() whenever a value chages.
>>>I think that you'd want to do a GETFLDSTATE(-1) in the grid's
>>>BeforeRowColChange...
>>Stopping the flow of a user in a grid with a dialog box constantly asking if
>>you want to save or cancel your changes would, in my opinion, greatly impede
>>the users ability to get work done.
>
>Very true. I was answering the question you asked, rather than thinking out
>what you really needed to know.
>
>So, what have your users decided they wanted?

No grid data entry. All use of grids for viewing. Our basic data, you know, those pesky little tables that hold contents of listboxes, etc each have a pageframe with two pages....page 1 is for single item data entry and page 2 has a grid from which they can view all the values or select one to edit if necessary. Much like TasTrade. Other data is of a complex enough nature to make it vastly simpler for a user to use a form rather than a grid.

I was also somewhat taken to task by Barbara Paltiel regarding my response to your question. I do apologize for any tone indicating that my way is the only way. She was of course correct, it is ultimately up to the users or whoever is writing the check for the application to decide what manner of data entry suits their needs.

On a personal note, I do try to avoid data entry in grids but I'll make whatever the client wants. I think that it is easier to write, maintain and enhance data entry forms rather than grids. Grids are already complex enough to deal with.

Steve