we use sequence tables (chained list:{actual,previous,next} ) in our SQL
migrated product to provide row-based navigation :-(.
can anybody explain, how professional business solutions implement:
- scrolling through e.g. customers
- changing ORDER BY
- go on scrolling from latest position (got under previous
ORDER-BY-sequence)
i have no idea doing this without seq. tables as bookmark persistency ends
with active HSTMTs.
thx², andy
__
andreas i. schmied +49-179-5981598 mailto:an...@arx.de (arx visions)