Dear Everyone. The following two details are not in dbforms documentation to the best of my knowledge and could very well effect the navigation on your pages.
#1] whereClause --- using this function renders navigation impossible! For instance, if you specify "where n>3" and your user views the page and then clicks the navNext button, the next page may show values where n is not greater than 3. Also, the whereClause can not be used with orderBy or filter attributes. They will be ignored. Order by should be used within the whereClause instead: whereClause="WHERE (FIELD1 >'25' AND FIELD1 <'50' ) OR FIELD2 NOT NULL ORDERBY FIELD7" ...So if you want to use navNext/navPrev buttons, you should use orderBy and filter attributes instead of a whereClause #2] orderBy -- if you use a non-primary key, you MUST specify sortable="true" within your dbforms-config.xml file. If you use orderBy with a non primary key and you don't specify that in the config file, then navNext/navPrev buttons will function like navLast/navFirst buttons and you will skip over results. If you are following these two rules and still have navigation problems, please let us know so that we can eliminate any bugs in dbforms navigation. Considerately, -- shawn <[EMAIL PROTECTED]> ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ DbForms Mailing List http://www.wap-force.net/dbforms
