Re: Forms master-detail multirecord query

Alex Filonov <afilonov_at_pro-ns.net> wrote in <948h1d$juk$1_at_nnrp1.deja.com>:

>on-populate-detail actually fetches all detail rows. If you show one
>only, then order them that row you need is the first in fetch. Just put
>an order by clause on detail block.
>
>In article <esp96.44543$68.6319719_at_typhoon.tampabay.rr.com>,
> micquest_at_tampabay.rr.com (McSteve-O) wrote:
>> Hello all. My eyes are sore from lurking, so I thought I'd post...
>>
>> In Forms, I have a master-detail record where the detail is queried
>> automatically by the master with the on-populate-details trigger that
 calls
>> query_master_details (the default forms way to populate the detail
 record).
>>
>> My situation is that the detail (persons address) can have more than 1
>> record match the master (persons name) record; as the case would be if
 the
>> person moved, I want to keep the history.
>>
>> The problem is that the query_master_details fetchs the first record
 (oldest
>> address) instead of the last record (current address).
>>
>> Is there a setting or quickie fix to change this to select the most
 recent
>> matching record, or will I need to PL/SQL the information myself, and
 if so,
>> any suggestions on how to go about it?
>>
>> TIA,
>>
>> Steve
>>
>
>
>Sent via Deja.com
>http://www.deja.com/
>

Thanks,
That was it. I don't why I didn't see that property field before in the block. Received on Fri Jan 19 2001 - 16:20:44 CST