| Preventing Form from thinking it's in 'changed' mode [message #526070] |
Sat, 08 October 2011 00:06  |
 |
dmillerp
Messages: 2
Registered: October 2011
|
Junior Member |
|
|
Simple question. I have a form with a block with a base table. This base table has some fields that I do not display, but instead display the 'user friendly' lookup value (via sql to a reference table). So my block has base table items and display items.
Now when I query the form it always thinks the records have changed because the non-base table items were fetched and placed on the form.
I've tried the code in the POST-QUERY and NEW-RECORD-INSTANCE triggers and both think that I'm trying to update base table data, which I'm not.
What suggestions do you have to prevent the form from thinking it's changed??
|
|
|
|
| Re: Preventing Form from thinking it's in 'changed' mode [message #526107 is a reply to message #526070] |
Sat, 08 October 2011 05:32  |
 |
Littlefoot
Messages: 21817
Registered: June 2005
Location: Croatia, Europe
|
Senior Member
Account Moderator |
|
|
Two options I can think of:- The first one is to
set_record_property(:system.trigger_record, 'block_name', status, query_status);
- Another one:
set_item_property(<item_name>, item_is_valid, property_true);
The first option might be simpler if there are many items you'd have to set valid.
[Updated on: Sat, 08 October 2011 05:33] Report message to a moderator |
|
|
|
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
