Hi Dirk. You were wright. The isKey attribute was not there, because the table itself did not have that field as a primary key and so, the dbtool did not pick that information automaticaly. I can now navigate without problems. After that, I roamed the User guide doc file and did not find that requirement. It should be added ! I propose at least adding to the CommonMistakes "Forgetting to add isKey="true" attribute to fields that are referenced in nested forms" By the way, is this a problem with nested forms only ?
Now I have another problem. The parent form has maxRows="1" while the child form has maxRows="3". However the information in the parent body is getting rendered as many times has the child body. This is happening with Tomcat 4.1.12 but not with an older version that I have which is 4.0.1. >From one of your latest mails you say that there is a problem with taglib pooling in 4.1.x. Is this a manifestation of this problem ? Is this a tomcat or a dbforms issue ? Can you provide more insight into this ? Thanks Carlos. Dirk Kraemer wrote: > > Hi Carlos! > > One thing that is needed when using nested forms is that > the referencing column for the table that is used > within the nested form has to be declared with isKey="true" > within config file. > Did you do that? > > If that's not the problem, could you tell us what > version of dbforms you are using? Can you locate > line 1641 within your version of DbFormTag.java? > Please do also activate debugging for log4j and > check what is written to the log. > > Regards > > Dirk ------------------------------------------------------- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0003en _______________________________________________ DbForms Mailing List http://www.wap-force.net/dbforms
