Hmmmm, these questions (this and Matt's previous) are interesting and
I'd also be curious about the answers. If you reply, please remember to
include the list. There are people out here watching...
Carl
Matthew Scholtz wrote:
>
> Another question for egroup types or other gurus:
>
> Doing ebase customization.
>
> Am puzzled by six (STORED) calc fields in Paymnts.102 , SCDef1Key . . .
> SCDef6Key. These contain the number 1 through 6 followed by the
> appropriate part of the source code for the payment. My question is: why
> do these fields have to be stored? They are used in six relationships
> which allow the description text for the six source code value pairs to pop
> up when you choose a SC. But for this they don't need to be stored. There
> are also relationships from SCDEFS back to Paymnts, but I can't see where
> these relationships are used... Can anyone help? We've got a large data
> set and are trying to pare down unneccessary fields.
>
> Also - is there a reason why SCPos1...SCPos6 in Paymnts are lookups instead
> of calced text functions of the Source Code field? Seems like lookups
> would be slower.
>
> Thanks,
>
> Matthew Scholtz
> San Francisco, CA
--
Carl Paulsen
New Hampshire Rivers Council
54 Portsmouth Street
Concord, NH 03301
603-228-6472
603-228-0423 Fax
[EMAIL PROTECTED]
