<i><font color="#663300">I'm updating some programs and would like to switch the data access from buffered tables to views.
For the form with one-to-many business objects, it's easy to change the many side to a view but I wander how to switch the primary object.
The way I have it now:
In admintoolbarbutton.click, I bring up a modal selection form. The user picks a record and then the default click (doform)is fired with a pointer to the proper record. When the form is table driven, the next/previous/first/last buttons just navigate through the table.
With a view, I would select only on record. Since the primary object is usually based on a very large table, I would not want to select it all.
Is there a way to preserve the navigation buttons in that environment?</font></i>
First, why do you want to preserve navigation across the entire table? Why not have the users select the records they are interested in?
If you are currently allowing users to navigate a huge table, a remote view of that table will not be a significantly bigger load on your network. So if the app absolutely <i>has</i> to allow them that kind of navigation, go for it.
However, with large data sets, it is almost always better to give users a way to select the record they want, rather than navigating record-by-record through a huge table. I typically remove the VCR-button navigation, and replace it with search forms.
<font color="#cc0000"> ___/
/
__/
/
____/</font>
Ed Leafe
©2001 Ed Leafe |
