> Is my observation correct, is the example given impossible, or am I > missing something? Is there a way to influence the fields used in the > SELECT clause? Yes, it's correct. Every table in dbform tag must be declared so that the framework can build the fields list. We need not only the fieldnames, the types are needed, too. So everything you want to use must be declared.
> Also, I tried a dbform tag with whereClause and tableList as > a sub- form. It seems that there is no relation made to the > parent dbform, > and the subform shows everything. How can I make this work? Do I have > to relate to the parent dbform myself in the whereClause? That can't work. whereClause and tableList overrides internal selections, so that you can not use both. For the subforms you need internal selections. Think about something like "freeform select" if you use tablelist and whereClause. You are able to to what ever you like, but you must do everything by yourself. What's about throwing away the whole freeform select stuff and declare everything as table or query in the config file? If this can not be done declare some views in your database. Then you can use all the navigation stuff of dbforms wihtout any problem. Regards, Henner ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ DbForms Mailing List http://www.wap-force.net/dbforms
