This a question for everyone:

I like the idea of sensitive result sets, especially sensitive views with lookup fields. But in most cases the data needs to be ordered for display
purposes by looked up values stored in other tables, so there is no index in the base table --> insensitive result set.  The big problem is not  
loosing sensitivity, but loosing edit-ability. Of course I can edit  the base table and reopen the query/view again, but it may be too long  for the
user to wait for, plus there are issues like repositioning all grids/trees/...  to the display exact same state as they were before editing. I was
thinking about  creating temporary tables / tables in memory DB  and setting up a triggers for automatic data synchronization on the record
level with the base table, but there maybe a better way. I was wondering how you guys would handle this situation?

With Regards,
Leslie

Tim,

What should happen if there is trigger for a regular table updating a temporary/Memory db table after a power fail? Does the engine some sort
of direct or indirect referential integrity check at  startup?

Leslie

I mean on the system data.

Leslie,

<< What should happen if there is trigger for a regular table updating a
temporary/Memory db table after a power fail? Does the engine some sort of
direct or indirect referential integrity check at  startup?  >>

I have no idea what you mean by those questions.  Could you give me an
example that will illustrate what you're talking about ?

--
Tim Young
Elevate Software
www.elevatesoft.com