I am currently migrating a 4.1.7 solution to Servoy 5.1.4.
We have a form that contains a related child tab within a footer. The body of this form displays the data correctly but will not allow for the user to scroll to view other columns outside of the viewing area. The child tab scroll bar is also not enabled.
Is there a reason why this is no longer working within Servoy 5.1.4? or is there a solution to this issue?
I have attached a picture of what I am looking to.
Basically I have my main form based on the order table.
The list on the left side is also based on the order table (no relationship).
The details on the top right is based on the order table as well. (no relationship).
Now the products tab is based on the products that were on that order. There is a relations ship 1-many orders_to_products_ordered
The parts tab underneath needs to display the parts with the products that were ordered. There is a relationship here which is product_to_product_parts
When the user selects and order, it will display the products, when the user selects a product from the product list it will display all the parts associated to that product selected in the list.
This used to work in a footer of the prodcuts ordered tab, but we are having all sorts of issues.
Could you provide a simple servoy solution example or a way to resolve this issue? We’ve tried the footer, which doesn’t seem to work in 5.1.4(problem seems to be the fact that the footer cannot be that large or the scroll bars will not work). Tried to use form based on products order table with two tab panels which doesn’t work because it requires the form to be in record view[attachment=0]untitled.JPG[/attachment]
I have noticed that the scrolling doesn’t work when the footer is greater than 100 pixels. If it is less than that the scrolling seems to be okay.
why not place in the order detail form (where you have that tabpanel with those 2 tabs i guess)
directly the 2 tabs? In 5 you can now place tabpanels multiply relations deep so that shouldnt be a problem.
I took your suggestion and based the containing tab form on the order, and then utilized the relationships as you had suggested for the two tabs on this new tab container form.