How are people handling multi-row viewing and editing these days?
Browse, grid, something else?

I need to have full validation.

I expect that I will use the dbc for the validation, but would
like the option to not have to 9as I might have some use that does not
use database tables).

If VFP version makes a difference, please specify that. I am
using VFP 6 SP 5.

Sincerely,

Gene Wirchenko

Computerese Irregular Verb Conjugation:
I have preferences.
You have biases.
He/She has prejudices.

I use the grid which has a VALID method available for each column's input
control. I also find myself using AfterRowColChange at the grid level to
detect movement from one record to another and to take any necessary action
such as updating controls that are not being displayed in the grid itself.

"Gene Wirchenko" <genew (AT) mail (DOT) ocis.net> wrote

"Jeff Grippe" <jgrippe (AT) hilldun (DOT) com> wrote:

How do you enforce row-level validation?

[snip]

Sincerely,

Gene Wirchenko

Computerese Irregular Verb Conjugation:
I have preferences.
You have biases.
He/She has prejudices.

"Gene Wirchenko" <genew (AT) mail (DOT) ocis.net> wrote

Forget the BROWSE, it is there more for backward compatibility than anything
else - you are better off using the grid. But I'm of the opinion that while
grids are fine for viewing multiple records, they are a poor interface for
editing. [When you're editing, prior or subsequent records should generally
not be part of your focus]. Instead, I use a read only grid and individual
(read/write) controls to echo (and edit) the currently selected record.

Others prefer to edit directly in the grid, but validation becomes more
complex.

You might check the FoxPro Wiki (as well as various framework sites) for
more discussion on this - it is a recurring topic.

- Rush

"Rush Strong" <rush.strong]@[verizon.net> wrote:

I thought of that (a long time ago) and discarded the idea as the
individual controls do take up a lot of space compared to a grid. I
suppose I could crunch the controls more than usual.

I do not think that the validation should be more difficult.
Unfortunately, it is.

Thank you.

Sincerely,

Gene Wirchenko

Computerese Irregular Verb Conjugation:
I have preferences.
You have biases.
He/She has prejudices.

"Gene Wirchenko" <genew (AT) mail (DOT) ocis.net> schrieb im Newsbeitrag
news:lbb2g0dj0m6m9umcvgistgt3bprddbqk4n (AT) 4ax (DOT) com...
From another posting
NODEFAULT
in yourGrid.BeforeRowColChange()
Assumed you have a boolean custom form property called
"EditMode", the condition could look like:
LPARAMETERS nColIndex

IF Thisform.EditMode
IF NOT INLIST(LASTKEY(), 13, 9) && enter & tab, to be continued
NODEFAULT
ENDIF
ENDIF
But I agree with Rush that validating and controling controls'
behaviour in a grid is at least more complicated than in a
separate "EditForm" or page.


hth
-Stefan

I agree with Rush that grids make poor data entry devices. One work around
after another and it still doesn't act as expected.

I acutally wrote my own data entry 'grid' consising of a container object
and multiple text boxes. When I get more comfortable that I've worked all
kinks out, I'd be glad to share it. But it acts more like you would expect
a grid type data entry screen to act.

--
Bill Browne
www.edgefinderstudios.com


"Rush Strong" <rush.strong]@[verizon.net> wrote