×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Sure your users may be used to a POSITION TO and being able to roll
backward. But that isn't the way to use SQL.
</Charles>
Positioning and scrolling forth and back could be done with SQL too!
You would simply need two cursors. One is limited down to the position and
the other up from the position. For a one field key very simple:
- cursor_up: select * from someView where some_key >= possition order by
some_key
- cursor_down: select * from someView where some_key < position order by
some key desc
For a compound key see my earlier post. Another solution would be to put the
keys together in the select statement to one compound (concat or something
like this). If you wanna make heavy use of this, put this logic in a data
access SRVPGM and call the position, getNext, getPrevies,... procedures from
your subfile programms. These DAO SRVPGMs would look very similar to your
programms of your business logic.
And best of it, you would get all additional funtionality of the power of
SQL on top!!!
D*B
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.
midrange.com
