In addition to what Frank and Michael said, you may want to have table
that just stores when the lookup table was last updated. When the app
detects that the value changed, then they know that combobox needs to be
refreshed with new/updated data.
Lets say you have a combobox listing the donut types available in the
shop, we get the last updated date:
select TimeOfLastUpdate from {StatusTable} where cSetting='donut';
If ever the above query changes the value of TimeOfLastUpdate, then you
know you have to query the {DonutsAvailable} table for the goal of less
data transfer.
On 05/21/2012 01:09 PM, Jeff Johnson wrote:
> My applications usually have a couple of main tables and several
> "lookup" tables that frequently change. Combo boxes are requeried on
> init, but when data changes in any of the tables the comboboxes need to
> be requeried to make the changes available. My question is, how often
> or when should combo boxes generally be requeried? On page refresh?
>
> TIA
>
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
