At 02:51 2013-11-26, Peter Cushing <[email protected]> wrote:
Gene Wirchenko wrote:
<snip>
The reason I want what I want is to make adjusting data much
easier. The app is client billing. There are various
dependencies that need to be manually verified. Any errors
detected have to be corrected. This is much easier when one can
see many rows at once.
There is a reason that browses are so useful; I simply want
something with better data validation.
Could you give an example of a row of data? What values each column
in the row has before the user gets to it and possible values to be
entered for each column. Hopefully that will show me why you need
to do it a certain way.
I have many browses that I would like to have row-level
validation for. I am trying to solve the validation problem in general.
The most important case is the work transaction table. It gets
data from DE and from importing from other systems used by the
company. All of this has to agree. Before invoicing, there is a
step we call "editing" where the data is checked for
consistency. This requires 1) being able to look at many rows at
once and 2) being able to edit the data. I want full validation in there.
One of the row-level validation rules required is that
basicchg+ovrhdefee=dsbamt+xsvamt
(Those are four columns of the table.)
Sincerely,
Gene Wirchenko
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
