Hello!
Background info
I am currently using Alpha Five Version 11 on a Microsoft Windows 7 desktop OS. I have recently run into what I believe may be a bug in the software related to customizing the buttons that appear on the javascript dialogs specified within a grid component.
Attached to this email is a zipped web project database that consists of a Microsoft Access database that contains two tables: Customers & OrderHeaders. The Customers table is a fictitious list of dummy customer data while the OrderHeaders table contains a fictitious list of dummy order header data. The Alpha Five database also contains two grid components: OrderHeader & CustomerLookup. The OrderHeader grid is based on the OrderHeaders table, and has an associated updateable detail view that allows you to update the order header customer id, order header customer name, order header customer address 1, and order header customer address 2. The CustomerLookup grid component is a read only grid component based on the Customers table. It shows the customer id, name, and address fields. Please see screen shot 'CustomerLookup.png' for an example of what the CustomerLookup grid looks like. The CustomerLookupGrid component is invoked from the OrderHeader grid component via a lookup definition specified on the �Ordhdrcustid� field on the OrderHeader component detail view. When the magnifying glass is clicked on for the lookup, the CustomerLookupGrid component gets displayed and provides you with the ability to select a customer via the �Select� link. From there, the customer id, name, and some of the address information is automatically populated into the respective fields on the OrderHeader detail view. This is all working OK.
Within the OrderHeader component, I have specified several javascript message overrides. This is normally specified under the �Javascript windows� area of the �Customization� section within any grid component. See attached screen shot 'JavascriptWindowsOptsShot.png' to see these overrides. In particular, I have also overridden the default OK/Cancel button options by replacing the �Ok� button text with �Yes� and the �Cancel� button text with �No�. This is circled in red within the screenshot.
Actual Problem
The problem I am having is that whenever I invoke the CustomerLookupGrid for the lookup from the OrderHeader detail view, select a customer, and then decide for example, to cancel the changes by clicking on the detail view cancel button, the confirmation buttons that get displayed on the javascript dialog are not Yes/No as I was expecting but instead Ok/Cancel. Please see screen shot 'DialogbuttonsWhenUsingCustomerGridLookup.png' to see exactly an example of this. If I had deliberately specified �yes/no� on the OrderHeader grid, that is what I am always expecting to be displayed but that is not happening in all circumstances. This problem does not happen, however, if I manually type in the data into the OrderHeader detail view and refrain from using the CusomerLookupGrid. Please see screen shot 'DialogbuttonsWhenNotUsingCustomerGridLookup.png' for an example of this. Where is it getting the �Ok/Cancel� from when using the lookup ? The only explanation I can think of here is that the OK/Cancel is originating from the CustomerLookupGrid and �overlaying� the �Yes/No� from the OrderHeader grid component. Why is it doing this when each grid has its own separate set of options ? As a side note, the message dialog text overrides are always being correctly honored regardless of whether the lookup is used or not.
I would appreciate it if other people, particularly the Alpha Technical support team, could attempt to reproduce this issue using my attached project files and let me know if they can reproduce it and whether it should be considered a bug. If not, why not ?
CustomerLookup.pngDialogbuttonsWhenNotUsingCustomerGridLookup.pngDialogbuttonsWhenUsingCustomerGridLookup.pngJavascriptWindowsOptsShot.png
Thank you.
Background info
I am currently using Alpha Five Version 11 on a Microsoft Windows 7 desktop OS. I have recently run into what I believe may be a bug in the software related to customizing the buttons that appear on the javascript dialogs specified within a grid component.
Attached to this email is a zipped web project database that consists of a Microsoft Access database that contains two tables: Customers & OrderHeaders. The Customers table is a fictitious list of dummy customer data while the OrderHeaders table contains a fictitious list of dummy order header data. The Alpha Five database also contains two grid components: OrderHeader & CustomerLookup. The OrderHeader grid is based on the OrderHeaders table, and has an associated updateable detail view that allows you to update the order header customer id, order header customer name, order header customer address 1, and order header customer address 2. The CustomerLookup grid component is a read only grid component based on the Customers table. It shows the customer id, name, and address fields. Please see screen shot 'CustomerLookup.png' for an example of what the CustomerLookup grid looks like. The CustomerLookupGrid component is invoked from the OrderHeader grid component via a lookup definition specified on the �Ordhdrcustid� field on the OrderHeader component detail view. When the magnifying glass is clicked on for the lookup, the CustomerLookupGrid component gets displayed and provides you with the ability to select a customer via the �Select� link. From there, the customer id, name, and some of the address information is automatically populated into the respective fields on the OrderHeader detail view. This is all working OK.
Within the OrderHeader component, I have specified several javascript message overrides. This is normally specified under the �Javascript windows� area of the �Customization� section within any grid component. See attached screen shot 'JavascriptWindowsOptsShot.png' to see these overrides. In particular, I have also overridden the default OK/Cancel button options by replacing the �Ok� button text with �Yes� and the �Cancel� button text with �No�. This is circled in red within the screenshot.
Actual Problem
The problem I am having is that whenever I invoke the CustomerLookupGrid for the lookup from the OrderHeader detail view, select a customer, and then decide for example, to cancel the changes by clicking on the detail view cancel button, the confirmation buttons that get displayed on the javascript dialog are not Yes/No as I was expecting but instead Ok/Cancel. Please see screen shot 'DialogbuttonsWhenUsingCustomerGridLookup.png' to see exactly an example of this. If I had deliberately specified �yes/no� on the OrderHeader grid, that is what I am always expecting to be displayed but that is not happening in all circumstances. This problem does not happen, however, if I manually type in the data into the OrderHeader detail view and refrain from using the CusomerLookupGrid. Please see screen shot 'DialogbuttonsWhenNotUsingCustomerGridLookup.png' for an example of this. Where is it getting the �Ok/Cancel� from when using the lookup ? The only explanation I can think of here is that the OK/Cancel is originating from the CustomerLookupGrid and �overlaying� the �Yes/No� from the OrderHeader grid component. Why is it doing this when each grid has its own separate set of options ? As a side note, the message dialog text overrides are always being correctly honored regardless of whether the lookup is used or not.
I would appreciate it if other people, particularly the Alpha Technical support team, could attempt to reproduce this issue using my attached project files and let me know if they can reproduce it and whether it should be considered a bug. If not, why not ?
CustomerLookup.pngDialogbuttonsWhenNotUsingCustomerGridLookup.pngDialogbuttonsWhenUsingCustomerGridLookup.pngJavascriptWindowsOptsShot.png
Thank you.
Comment