![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I have a combo box that its value is used to calc another value on the form. works fine until someone wiped the value from the box and hits tab. if the drop down showed a value such as 50 and the calculations are done on that value. if they wipe it and exit the box the calculations are still done on the 50 on after update. any way to get the timing correct with this type of thing so that when they remove the 50 and exit it is now a null and no calcuations are done? In the AfterUpdate event of the combo something like |
#3
| |||
| |||
|
|
sparks wrote: I have a combo box that its value is used to calc another value on the form. works fine until someone wiped the value from the box and hits tab. if the drop down showed a value such as 50 and the calculations are done on that value. if they wipe it and exit the box the calculations are still done on the 50 on after update. any way to get the timing correct with this type of thing so that when they remove the 50 and exit it is now a null and no calcuations are done? In the AfterUpdate event of the combo something like Me.CalcField = Me.SomeField * NZ(Me.ComboFld,0) |
#4
| |||
| |||
|
|
after update If (Me!FullVal.Column(1) = 20) Then Me.Final = (.335 X 20) the problem is you put in debug.print Me!FullVal.Column(1) pick the 20 and debug.print shows 20 on afterudate |
|
remove the 20 and leave and it will debug.pring 20 again even though the value was cleared. I am not sure if the value is actually recorded at a later time or what. I need to run and try on exit or lost focus On Wed, 08 Sep 2010 07:34:52 -0700, Salad <salad (AT) oilandvinegar (DOT) com wrote: sparks wrote: I have a combo box that its value is used to calc another value on the form. works fine until someone wiped the value from the box and hits tab. if the drop down showed a value such as 50 and the calculations are done on that value. if they wipe it and exit the box the calculations are still done on the 50 on after update. any way to get the timing correct with this type of thing so that when they remove the 50 and exit it is now a null and no calcuations are done? In the AfterUpdate event of the combo something like Me.CalcField = Me.SomeField * NZ(Me.ComboFld,0) |
![]() |
| Thread Tools | |
| Display Modes | |
| |