IDE Application Tree

[Keith]

I wouldn't mind understanding more about the way in which the Application Tree is generated for an NT application.

I created a test dictionary with 3 tables related 1:Many (Customers/Bookings/BookedPets).  I then used the Wizard to create an app with only Customers selected and got two procedures BrowseCustomers and UpdateCustomers. Great.

Next I generated a new app with Customers and Bookings selected and I got the tree in the Wizard1 picture.  A third app with all tables selected produced the tree in the Wizard2 picture.

'Common sense' (dangerous I know) indicates that the tree would be:

BrowseCustomers
  UpdateCustomers
     BrowseBookings
         UpdateBookings
             BrowseBookedPets
                 UpdateBookedPets

since that reflects the relationships and the way the browses and forms are presented as you work through the application but instead the tree seems to be upside down (BrowseBookedPets first) and there are all of these secondary instances (recursive) of the procedures.

The real app that these tables came from now has a dozen tables and the Tree is a dogs breakfast and I recently add three tables and almost doubled the number of displayed procedures.

So I just wondered what is happening and whether there is anything to be concerned about and whether it is normal to have this multitude of procedures.

Thanks

Keith

[attachment deleted by admin]

[MyBrainIsFull]

Without seeing your DCT its hard to make an educated comment, but it looks ok to me from your images. 

What you are seeing is the customer from the pets eyes, ie. it looks upside down because the proc you are basing this on is at the pet level.

So from browse pets, the pet has a booking, and that booking was made by a customer, and this is why you think its upside down

You would probably have done better making the pet the child of the customer, and the booking as the child of the pet

As one customer has many pets,
The pet has one owner but has many bookings

Hope this helps

PS was the reference to a "dogs breakfast" an intentional pun for an app that books in pets?

[Bruce]

the easiest way to understand the tree is just to look at the fields on the form, or the settings on the browse. Obviously a browse calls a form, but forms have lookups which in turn are browses.

So usually you can follow the logic just by looking at the fields on the form.

cheers
Bruce