I have three levels of nested tables in a single form. Somehow, the record shown for middle level table (maxrow=1) does not relate to the first level, meaning, parent child relationship is not being maintained...
Regards
Vinoth
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Have included "whereClause" attribute in the middle level dbForm. When this is done, the "parentField" and "childField" attributes of the middle level dbForm isnt maintained and only the whereClause specified now is along maintained.
When explicitly included the relation(parent-child) in the whereClause along with the existing clause, it seems to work fine.
1) Is this the only way out or is there an optimum way to achieve this?
2) When whereClause attribute is used, will it over ride the parent-child relationship ?
How do we over come this?
Thanks in advance.
regards,
vinoth.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
whereClause overrides everything!
This is for freeform select only - so you can not use it with parent-child relations.
See docs for detail.
If you need filtering use some of the other filter methods.
Henner
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
I have three levels of nested tables in a single form. Somehow, the record shown for middle level table (maxrow=1) does not relate to the first level, meaning, parent child relationship is not being maintained...
Regards
Vinoth
Never tried 3 levels of nested tables.
Could you try to reproduce this with an bookstore based example?
Then i could try to fix it.
Henner
Hi,
Have included "whereClause" attribute in the middle level dbForm. When this is done, the "parentField" and "childField" attributes of the middle level dbForm isnt maintained and only the whereClause specified now is along maintained.
When explicitly included the relation(parent-child) in the whereClause along with the existing clause, it seems to work fine.
1) Is this the only way out or is there an optimum way to achieve this?
2) When whereClause attribute is used, will it over ride the parent-child relationship ?
How do we over come this?
Thanks in advance.
regards,
vinoth.
whereClause overrides everything!
This is for freeform select only - so you can not use it with parent-child relations.
See docs for detail.
If you need filtering use some of the other filter methods.
Henner