Re: F45. Problem using display_item fields in enter_query mode.

In article <VI5XQBASS5j3EwvG_at_ahardy.demon.co.uk>, Andy Hardy <aph_at_ahardy.demon.co.uk> writes
>In article <7mo1aj$cjo$1_at_hole.sdsu.edu>, Isaias Gutierrez
><igutierr_at_mail.sdsu.edu> writes
>>Try making your description field (in the item property) very long, and see
>>if it pulls in the description after that.
>>
>
>Tried it with 2000 characters for a 40 character db column whose
>contents are only usually 10...
>
>Strange how it works OK during update...
>
>Andy

Further playing seems to show that it's not possible to use the LOV to enter a value into a display_item of the *same record* during enterquery...

Andy
>>
>>Andy Hardy <aph_at_ahardy.demon.co.uk> wrote in message
>>news:b5zuEBAk1xj3EwNR_at_ahardy.demon.co.uk...
>>> Hi,
>>>
>>> I have a block alone the lines of:
>>>
>>> pk_id, fk_id, fk_description
>>>
>>> where the foreign key id is not displayed, but it's value is put in
>>> fk_description (a display item) through a post-query.
>>>
>>> I have a when-mouse-doubleclick on the fk_description which brings up a
>>> LOV of the foreign key values and on selection both fk_id and
>>> fk_description get set.
>>>
>>> This works fine until I use enter-query mode. At this point the LOV
>>> appears correctly, but when I select an item I get a FRM-40831 for the
>>> description field. This is saying that the value being read into the
>>> item is too long and it has been truncated. In fact the description
>>> field is now blank, but the fk_id has been given its value.
>>>
>>> Any thoughts?
>>>
>>> Andy
>>> --
>>> Andy Hardy. PGP key available on request
>>> ===============================================================
>>
>>
>

-- 
Andy Hardy. PGP key available on request
===============================================================