Re: F45: LOV for validation updates all my records!

In article <roHP3.6$1b.71_at_nntp.csufresno.edu>, Steve Cosner <stevec_at_zimmer.csufresno.edu> writes
>In article <LCTwyDA6MzD4EwxP_at_ahardy.demon.co.uk>,
>Andy Hardy <aph_at_ahardy.demon.co.uk> wrote:
>>Hi,
>>
>>I have a form based on a two value table. Each of the two values is
>>allowed a set number of distinct values so I use a LOV linked to an RG
>>that takes its values from the database.
>>
>>When I execute_query, it would appear that each record is being
>>validated during the query (lots of flickering cursor!). When I make a
>>change and save it, I get a message that says, in effect, all records
>>loaded to the form have been updated (even though none of them appear to
>>have changed).
>>
>>How do I get around this? I only want the validation to be carried out
>>for new data entries.
>
>
>It sounds like you have a post-query trigger that is setting a field
>in the block. This will cause validation to occur.

You are quite correct - I'd assumed that the validation would only occur against the base table items.

> Try checking
>:system.form_status in your when-validate triggers, or maybe set record
>status back to query at the end of the post-query trigger. You can
>also dynamically turn on or off the LOV Validation property on an
>item.

Yes, using set_record_property to set the status back to query does the trick.

>
>I don't understand what the "flickering" would be caused by.

I assumed something to do with LOVs resetting the values... but it's not very repeatable!

Many thanks,

Andy
>
>Steve Cosner

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