Thanks Jimmy.
I know for the sake of purity, I probably should be using straight XML for my data sources, but what I neglected to tell you (im sorry) is im using an Access 2007 DB (to be exported to SQL server in the future).
But, I did figure out how to do what I am looking for with a confirmation button and rules.
Basically what I did was set up a button with the following rules:
- sum(@Price[@Product = InletSensors[//InletSensors != ""]]) <!-- Just looking for NON blank values in the Multi-Select Box to match to my Secondary Data Source's Price List as per my previous post-->
- InletSensorConfirm = true()
- The only conditional on the rules was that InletSensorConfirm = FALSE
The Second rule refers to a boolean drop-down list box ( as opposed to a check box) that had its conditional display settings set to be hidden - whether it was true or false. ( so as to hide it at all times from the end user). It has a default value of false() I use this control to toggle whether the user has 'Confirmed' their selections in the multi Selection box. If it is = true() i disable the multi-select box.
I tried to apply the first rule to the multi Selection List Box itself and found the following - what I call - 'Quirk': Anytime I selected a value in the Multi Select Check Box as 'CHECKED', the rule would run and the proper total was calculated (Great!), but when any of the 'CHECKED' values were Un-CHECKED the rule would not recalculate (thereby causing the total field to remain as though nothing was un-CHECKED) until any other option, including the one I just Un-CHECKED was set to CHECKED. There were no conditions on the rule running.
That simply could not work since I am not assured that the salesperson using the form would mark anything else CHECKED after un-checking something.
If you have any thoughts on how I could remove the hidden toggle field so that the rule runs at all times, whether or not another item is checked as described above.
Thanks again!
-Fritz