Subject Re: GRID
From Eugene Wright <ekwright7@gmail.com>
Date Sun, 15 Apr 2018 13:01:45 -0400
Newsgroups dbase.getting-started

I get around this by writing to temporary tables and locking columns that I don't want the user to edit by setting them to 'read only'. I can then do error checking on the data before saving it to the permanent record usually via a 'save' pushbutton.


Mervin Bick Wrote:

> On 2018-04-04 9:56 AM, MUSTANSIR GHOR wrote:
> > Dear Mervyn
> >
> > I remember one time you mentioned to use grid not datalinked to rowset. Can you set small example how this can be done.
>
> That's not quite what I said.
>


> I said that I'd found it was too easy for the user to make mistakes when
> editing in a grid especially where one used a combobox as the editor
> object for a cell.  Based on this I never use a grid for data entry or
> editing.  I always do data entry and editing in entryfields and/or
> comboboxes.
>
> Because I'm trying to make code I write for myself "SQL server ready"  I
> don't use datalinked entryfields or comboboxes.   On the other hand, if
> the code is never going to use data from a SQL server datalinked
> entryfields and comboboxes save a lot of coding.
>
> A grid can ONLY display data from a datalinked table.   If you want to,
> say, display data from an array in a grid you first have to write the
> array out to a temporary table.
>
> I'm not too well at the moment and I can't spend as much time at the
> computer as I would like.  I will, however, try and create a little
> example for you soon.
>
> Mervyn.
>
>