Our company has developed a whole CRM using dbForms and has been in production for around 1 year, but now we are having perfomance problems with big tables.
Are you using 1.1.4 or later with the DataListNavigation system? It is the default since around 1.1.4 -- maybe 1.1.4pr2 or so. Anyway, it is known to cause performance problems with big tables if you do not have sufficient memory. The solution would be to go back to classical nagivation. See the chapter on Navigation under Major New Features. Geez maybe that should be moved into its own section since it isn't really new anymore...
Also, in tableData and related tags, you may want to disable the cache if again memory is scarce.
Another thing I do with a table that has 165,000+ rows is use the DataListNavigation but to filter the query before it is run the first time so the rsv that gets stored is managable memory wise. Otherwise with no filter I need classic navigation to avoid a three minute wait.
-- Shawn
Karma is immutable, so act accordingly!
------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com _______________________________________________ DbForms Mailing List
http://www.wap-force.net/dbforms
