Or a refinement on my previous thought: assuming I'm not mistaken about not being able to scroll out of the result set, I could have two result sets open: one starting with the current key value, and one ending with the current key value: when I scroll backward, I reopen the "starts with current key value" result set, to reflect the new current key value; when I scroll forward, I reopen the "ends with current key value" result set, and if I jump to user-specified key value, I reopen both.

That could work. People said that running a script interpreter with a recursive-descent parser as a trigger program couldn't possibly work, and yet it works (and doesn't cause nearly as bad performance hits as doing the wrong operations on SQL views in which fields are processed through UDFs).

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.