At 11:14 AM 11/2/00 -0800, you wrote:
>At 10:42 AM -0800 11/2/00, Matthew Scholtz wrote:
>>At 05:21 PM 11/1/00 -0800, you 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.
>>>
>>>Is that right? I though key fields had to be stored and indexed.
>>
>>Well, by theory they should be. But a relationship in FMP really
>>only needs the right side to be indexed. If you're going to do a
>>find on the related field(s) then you need the left side indexed as
>>well. But if it's only to display a line of text (as this seems to
>>be) there's no need to index the LH side. What puzzles me in this
>>case is that there's relationships in SCDEFS back to Paymnts (so
>>these fields end up on the RH side as well), but I can't find
>>anywhere where those relationships are used.
>
>I know you get a warning if you try to delete a source code that's in
>use. That probably looks for a record in paymnts that has the source
>code. Is that where they're used?
I don't think you'd need these for that, since they are relationships between the
individual code pairs and the DEFINITION of the pair level. It's a relation to the
SRCDEFS file, not the Solicit file, which contains the source codes themselves. For
Solicit to find if a source code was in use, it would only need a relationship to the
whole source code (which is indexed) and not to the individual code pairs.
>>>>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
>> >
>> >--
>> >Dave Shaw Northwest Classics, Inc
>> >tel: 206-954-7526 fax: 206-625-1338
>> >
>> >
>
>--
>Dave Shaw Northwest Classics, Inc
>tel: 206-954-7526 fax: 206-625-1338
>
>
