Tweet
Re: Conditional browse not properly filtering records based on another browse’s value
I want to document the solution to the problem I posed yesterday. This breakthrough was made possible by my new understanding that Alpha Five allows parent and children records to be linked on compounded keys.
Here is my revised set definition:
tblPerson (Person_Id)
----tblPersonProfile (Person_Id, Profile_Id, 1:M)
--------tblPersonProfileItem (Person_Id, Profile_Id, Item_Id, 1:M)
------------tblProfileItem (Profile_Id, Item_Id, 1:1)
--------tblProfile (Profile_Id, 1:1)
The 1:1 relationships are necessary to display the respective descriptions of the profile or of the item.
I generated my default form before I added the 1:1 relationships, added these relationships to the set, then used the Toolbar's Drop List to place the description of the Profile and the ProfileItem in the two browses. The top browse is the equivalent to a set of tabs and the bottom browse represents information that would be displayed on that tab.
The result is perfection!
Below is a screenshot of the finished product.
I will set the width of the Person_Id, Profile_Id, and Item_Id in the browses to zero and hide the Person_Id at the top of the form for a more finished appearance. I will move the description of the Item to the left of its value. But I have left them exposed to allow you to see better what I did.
ALL WITHOUT A SINGLE LINE OF CODE!!!
All this is embryonic, but you may appreciate that allowing your user to add their own profiles and to assign their own items to a profile (using a form yet to be developed), your user can effectively "customize" your Alpha application.
This is ever more elegant that plopping down fields User 1, User 2, User 3, etc down on your form and allowing the user to change the labels.
Bob McGaffic
Pittsburgh, PA
Screen 1: Shows Clothing sizes profile for person 0000000000000000
Screen 2: Shows Schools attended profile for person 0000000000000000
Screen 3: Shows Clothing sizes profile for person 0000000000000001
I want to document the solution to the problem I posed yesterday. This breakthrough was made possible by my new understanding that Alpha Five allows parent and children records to be linked on compounded keys.
Here is my revised set definition:
tblPerson (Person_Id)
----tblPersonProfile (Person_Id, Profile_Id, 1:M)
--------tblPersonProfileItem (Person_Id, Profile_Id, Item_Id, 1:M)
------------tblProfileItem (Profile_Id, Item_Id, 1:1)
--------tblProfile (Profile_Id, 1:1)
The 1:1 relationships are necessary to display the respective descriptions of the profile or of the item.
I generated my default form before I added the 1:1 relationships, added these relationships to the set, then used the Toolbar's Drop List to place the description of the Profile and the ProfileItem in the two browses. The top browse is the equivalent to a set of tabs and the bottom browse represents information that would be displayed on that tab.
The result is perfection!
Below is a screenshot of the finished product.
I will set the width of the Person_Id, Profile_Id, and Item_Id in the browses to zero and hide the Person_Id at the top of the form for a more finished appearance. I will move the description of the Item to the left of its value. But I have left them exposed to allow you to see better what I did.
ALL WITHOUT A SINGLE LINE OF CODE!!!
All this is embryonic, but you may appreciate that allowing your user to add their own profiles and to assign their own items to a profile (using a form yet to be developed), your user can effectively "customize" your Alpha application.
This is ever more elegant that plopping down fields User 1, User 2, User 3, etc down on your form and allowing the user to change the labels.
Bob McGaffic
Pittsburgh, PA
Screen 1: Shows Clothing sizes profile for person 0000000000000000
Screen 2: Shows Schools attended profile for person 0000000000000000
Screen 3: Shows Clothing sizes profile for person 0000000000000001
Comment