The database maintenance design pattern that I follow (almost religiously)
is the use of a browser component that is based on an HTML table (except it
also implements row navigation and selection via keyboard and mouse event
handlers, which facilitate database operations such as copy, change, and
delete). On the server, we implement scrollable cursors via SQL. In the
browser we implement a scrollable list that asynchronously syncs with the
scrollable cursor on the server. Provide column sorting. Provide a dialog
for filtering the list. As users navigate from row to row in the list, the
complete record is automatically and asynchronously retrieved from the
server via an RLA operation, and shown in a panel which is placed above, or
aside the list. Keyboard and mouse event handlers toggle the UI between
add, copy, change, and delete modes.


On Tue, Dec 31, 2019 at 11:38 AM Booth Martin <booth@xxxxxxxxxxxx> wrote:

OK. I like that.

Question: we're using one of these new & spiffy solutions. We want to
provide the same function as our antiquated 5250 subfile but jazz it up
with that modern stuff. And we have a 1,600,000 row DB/2 table. What
steps, generally, do we do differently than we'd do with a 5250 solution?


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.