The worst case is when there are no navigation buttons (it may happen ini think the common goal is that the user wants to SEE the freshly inserted data. So, in singleform scenarios, it is completely desireable to navigate to the freshly inserted data. However, i do share your concern about the scenarios where you deal with endless forms ( maxRows="*") ; in that case, navigation is counterintuitive; we really need to render all records, otherwise, yes, the helpdesk phone will start ringing ;-)
circumstances where few records are expected so that maxRows dbform attribute
is set to "*"): in such situations there is no way to redisplay all the
records, other than reloading the form, and this cannot be done safely
because, in general, browser reload button will repost data to the server...
a bit confusing, i think.
Better could be if, following an insert event, the form could be positioned to the last page (according to the maxRows settings), and not to the last record alone. It sounds good? Is this feasible?
Therefore, i committed a little patch to DbForms tag into CVS which should address the problem concerning the endless forms. Please let us know, if this solves some of the problems you reported.
cheers Joe
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ DbForms Mailing List
http://www.wap-force.net/dbforms
