Hi all, just tested last revision of DbFormTag that fixes the bug "insert and delete event always shows first page instead of current page". (Not yet available thru anonymous CVS, but i hack my snapshot with changes logged on Jdbforms-developers mailing list)
Problems on parent form positioning has been solved, but i think there are some usability problems still remaining when INSERTING new records. I'll try to explain my points here:
When adding new records using an insert button, the new first position of the form points to the record just added. This could be ok (and even usefull!), but the form redisplay itself showing only the new record if table ordering causes it to be the last one (very common case when natural ordering is used). I think users can be extremely confused by that because: "all other records that were previously here seems to 'magically' disappear!" - i can already hear customers calling me at the help-desk... ;)
The worst case is when there are no navigation buttons (it may happen in 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?
In any case, thanks a lot to everyone for the BIG work on DbForms!
Regards, Roberto
------------------------------------------------------- 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
