BenHayat wrotejohntalbott wroteeagles9999 wrote
Additionally.... you will probably (and in many cases should) change your app to take advantage of some of the new features... ie. Nested Queries, Modeless WIndows etc.
What do you mean by Nested Queries?
Thanks,
JT
What he means, is that in your query grid, each row can be set to open up another query. For example your primary query may show a list of customers. Each customer may have orders and order may have line items.
You can turn or the "Expand on Row" feature for the first query to show an Order query. This way, when user expands a customer's row, they can see all the orders for that customer. Similarly, for each order you can do the same and show line items. The nested feature doesn't have to be only a query. You can even edit customer details on expansion.
Very powerful.
Thanks Ben. I've been testing that.
I've ran into an issue where after "Expand On Row" the parent was no longer in context for the where clause of the Child query. I'm not sure if that's a bug / known issue.
I switched to displaying a Parent form that in turn just displays a table of Children as a reference attribute. I'm not finished with it. It's seems like it may work, but it's clunky.
Another factor is that I'm using inline editing for the tables. I don't want to have to open a form as there are only a few attributes to enter at each level.
