Steven,
I'm working on a database app myself right now. I'm
using the built-in database but only for prototyping.
I'm assuming I will also not have all the move
next/previous etc. like you describe.
I decided that rather than grab all the row ids, I
would present a blank screen. The user would either
enter a new record or use the find ability to find the
desired record to edit. I will add a search command to
allow collection of a subset of rows (where I will be
collecting row ids), but my experience is that few
users (none?) actually use the next/previous features
I have provided (when I use FoxPro).
It might also be useful to discuss some basic UI
design features (e.g. menus) on this list. I have seen
lots of database-based apps done in lots of languages
and very little consistency.
-Bob Gordon
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
|