El_Pablo Posted December 24, 2009 Share Posted December 24, 2009 I think a new layout part should make it's way to the next version. A body part that act like a portal. This could be useful for a master-detail layout. Instead of a portal with a fix number of rows that fills the body, this body-portal part could be link to the child data from the layout table. What do you think of this idea? Link to comment Share on other sites More sharing options...
Lee Smith Posted December 24, 2009 Share Posted December 24, 2009 Have you tried making a List View Layout? Link to comment Share on other sites More sharing options...
El_Pablo Posted December 24, 2009 Author Share Posted December 24, 2009 I know that there's always a workaround with list view. The problem with a list view it that each record can have a different parent. It's a PITA to create an invoice using a listview. Since all the records can belong to a different invoice. We always have to filter the data using some sort of script and block search in that layout and so on. If a body-portal part existed, we could simply link a table to the layout and a related table to the body-portal part. It would be much more easier to control the layout. Access has something like this in it and it's called a subform... so why not a sublayout in FM? Link to comment Share on other sites More sharing options...
bcooney Posted December 24, 2009 Share Posted December 24, 2009 "It's a PITA to create an invoice using a listview." Really? Simply gtrr Invoice > InvLineItems, and print. Link to comment Share on other sites More sharing options...
El_Pablo Posted December 24, 2009 Author Share Posted December 24, 2009 I know all these tricks. My suggestion is to save some development time using a subform part. Each new version of FM needs some improvement. Link to comment Share on other sites More sharing options...
bcooney Posted December 24, 2009 Share Posted December 24, 2009 I agree, every developer has their list of wants and wishes. However, I don't see why you need this. Reporting from a child table isn't a "trick" imho. Link to comment Share on other sites More sharing options...
El_Pablo Posted December 24, 2009 Author Share Posted December 24, 2009 Sure every developper has there own wishlist. The problem using a list report for child data, is the maintenance and management of all the constraint we want to implant to the user. By example, if the user want to view an invoice and the invoice lines are in a list view layout. What prevent the user to show all the data using "Show all record" or the CTRL+J keystroke? - Managing the rights for this layout and/or data, but what if he really needs to see some specific invoice lines in a way we couldn't image? All this management make me lost some development time... Anyway, it was just a wish! Merry Christmas to all! Link to comment Share on other sites More sharing options...
Jalz Posted December 29, 2009 Share Posted December 29, 2009 Well I for one would also like this : Link to comment Share on other sites More sharing options...
Recommended Posts
This topic is 5234 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now