This problem was first mentioned last week - see msg #31053. Using build 1454-1042. The sort order specified in form properties for displaying child records in an embedded browse on a form does not work properly. Child records will only display in record number order. Setting record order in the set link definition results in no child records being displayed in the embedded browse.
In my 'musicians' database, I have a set to track which players are performing in a particular concert. I use this set to prepare the personnel rosters for our concert programs, and also to generate mailing and call lists and provide email links for those occasions when we have to contact players quickly for weather cancellations, rescheduling of rehearsal dates or venues, etc. (we had quite a few of these occasions in Connecticut this past season).
The parent table is 'concerts', linked one-to-many to 'concert_link', which has one-to-one links to 'players' and 'instruments'. 'Concert_link' should provide the sort order for the embedded browse on the form. Records in the embedded browse should display sorted by instrument section and seating position. This provides the same display order that is used for the personnel roster printed in our concert programs. To do this, I have used the expression 'instrument_code'+'part'+section_position', all character fields. The 'part' field is only used for violin I and violin II. For example, principal 2nd violin would be '01II1', 2nd clarinet is '302' and 4th horn is '604'. Setting this order expression in the form properties worked fine until I installed the latest build.
For each concert, I start with a core of 46 active players. I keep a master table with records for this core group, using the same table structure as the 'concert_link' table. I update the records in this master table with the current concert code and then append all records to the 'concert_link' table. Then I update the appended records for any wind or percussion player who will have a substitute for the concert and delete records for any string player who will not be playing. Finally, I add records for any extra players who will be joining us for the concert. This usually results in some extra string players' records being added at the end of the table.
To keep track of how many players in each section have connitted to play, I really need to see each section's players grouped together. I can do this in a report, of course, but it is inconvenient to have to print out and refer to a report each time I need to work with a concert's records.
Was this change in Alpha5 behavior planned, or was it an unexpected side effect of some other change? Is anyone at Alpha working to change it back to the way it was? Does anyone have any suggestions as to how I can get the records to display in the sort order I need?
Thanks.
Sherrill
In my 'musicians' database, I have a set to track which players are performing in a particular concert. I use this set to prepare the personnel rosters for our concert programs, and also to generate mailing and call lists and provide email links for those occasions when we have to contact players quickly for weather cancellations, rescheduling of rehearsal dates or venues, etc. (we had quite a few of these occasions in Connecticut this past season).
The parent table is 'concerts', linked one-to-many to 'concert_link', which has one-to-one links to 'players' and 'instruments'. 'Concert_link' should provide the sort order for the embedded browse on the form. Records in the embedded browse should display sorted by instrument section and seating position. This provides the same display order that is used for the personnel roster printed in our concert programs. To do this, I have used the expression 'instrument_code'+'part'+section_position', all character fields. The 'part' field is only used for violin I and violin II. For example, principal 2nd violin would be '01II1', 2nd clarinet is '302' and 4th horn is '604'. Setting this order expression in the form properties worked fine until I installed the latest build.
For each concert, I start with a core of 46 active players. I keep a master table with records for this core group, using the same table structure as the 'concert_link' table. I update the records in this master table with the current concert code and then append all records to the 'concert_link' table. Then I update the appended records for any wind or percussion player who will have a substitute for the concert and delete records for any string player who will not be playing. Finally, I add records for any extra players who will be joining us for the concert. This usually results in some extra string players' records being added at the end of the table.
To keep track of how many players in each section have connitted to play, I really need to see each section's players grouped together. I can do this in a report, of course, but it is inconvenient to have to print out and refer to a report each time I need to work with a concert's records.
Was this change in Alpha5 behavior planned, or was it an unexpected side effect of some other change? Is anyone at Alpha working to change it back to the way it was? Does anyone have any suggestions as to how I can get the records to display in the sort order I need?
Thanks.
Sherrill
Comment