A5V5 Latest on XP
I have been searching for notes on the below but can't seem to find what I am looking for - probably due to the volume of notes on embedded browses.
Lets take a form based on a table (not a set) - say the customer maintenance Form in Alpha Sports:
The browse display behavior seems to vary depending on whether you delete a record via parent level using a button event and using right click delete (right click delete also varies depending on what has focus).
If I add a button with a Delete Record action at the parent level, then when I delete the current record the browse display refreshes to display the first record - rather than holding its position in the browse. If I specify an embedded layout level delete on my button then it deletes the record and does not redisplay the browse from the first record (what I want).
If I select another customer in the browse and then right click in some white space on the the Form and select delete, the current record is deleted and the browse refreshes with the current record gone but the browse does not redisplay from the first record in the table (assumably the browse still has focus from where I initially selected the customer to delete). But, if I select a customer in the browse, click on a field in the Form proper and then right click in some white space on the form (not over the field) then the current record is deleted and the browse is refreshed from the first record in the table.. Grr .
I don't understand why the browse display behavior is or should be different - it sure frustrates my users..
The variances in behavior deepens on Forms based on sets with an embedded browse (based on the parent table in the set).
with one Form, I can't use the delete on the embedded layout level (it does not delete the currently selected record and I have checked that the browse is based on the parent table in the set). They can only right click delete when the Form has focus. A delete event on a button in such a form must use the delete parent level action but the browse is redisplayed from the first record in the browse. Yet on another Form (based on a different set) I can use the delete at embedded layout level on a button event and the browse behaves as desired (although the browse behavior after a right click delete still varies).
Is there a solution to presenting the user with a consistant browse display behavior across all methods of deleting a record in a Form?
Regards,
Scott
I have been searching for notes on the below but can't seem to find what I am looking for - probably due to the volume of notes on embedded browses.
Lets take a form based on a table (not a set) - say the customer maintenance Form in Alpha Sports:
The browse display behavior seems to vary depending on whether you delete a record via parent level using a button event and using right click delete (right click delete also varies depending on what has focus).
If I add a button with a Delete Record action at the parent level, then when I delete the current record the browse display refreshes to display the first record - rather than holding its position in the browse. If I specify an embedded layout level delete on my button then it deletes the record and does not redisplay the browse from the first record (what I want).
If I select another customer in the browse and then right click in some white space on the the Form and select delete, the current record is deleted and the browse refreshes with the current record gone but the browse does not redisplay from the first record in the table (assumably the browse still has focus from where I initially selected the customer to delete). But, if I select a customer in the browse, click on a field in the Form proper and then right click in some white space on the form (not over the field) then the current record is deleted and the browse is refreshed from the first record in the table.. Grr .
I don't understand why the browse display behavior is or should be different - it sure frustrates my users..
The variances in behavior deepens on Forms based on sets with an embedded browse (based on the parent table in the set).
with one Form, I can't use the delete on the embedded layout level (it does not delete the currently selected record and I have checked that the browse is based on the parent table in the set). They can only right click delete when the Form has focus. A delete event on a button in such a form must use the delete parent level action but the browse is redisplayed from the first record in the browse. Yet on another Form (based on a different set) I can use the delete at embedded layout level on a button event and the browse behaves as desired (although the browse behavior after a right click delete still varies).
Is there a solution to presenting the user with a consistant browse display behavior across all methods of deleting a record in a Form?
Regards,
Scott
Comment