If your workaround works, I'd say you'll have to live with it. Sometimes, it's not for us to know the "why". (though that causes me sleepless nights) ;)

>The problem is that when I step through it myself and emulate the user's steps, I cannot duplicate. As soon as the control loses focus, the value is stored in the variable. It is stored during interactivechange too. I have turned on the coverage profiler and checked also. However, it appears that in the runtime at the user's site it intermittently does not store the value even after the valid and lostfocus have fired. I know this is happening because I have seen it with my own eyes but trapping it in the program programmatically seems virtually impossible because it always stores when I attempt to trap for it.
>
>
>>Have you checked that when you get to the control on the second page, that the first control's value has been updated? This may not have anything at all to do with your ToolBar.
>>
>>
>>>No code at all in the lostfocus or valid. No code in any method of this control as a matter of fact. I just now entered code in its interactivechange event that forces the value of the control to be stored to the control source but that should not be necessary. It does force the storing of the value but that is only a workaround.
>>>
>>>the control's controlsource is map_time and I put in the control's interactivechange:
>>>
>>>map_time = this.value
>>>
>>>now the value the user entered is always stored to map_time but that should not be necessary.
>>>
>>>>On the surface, that should be the case, leaving the page and entering text in the control on the second page should force the update of control 1. Do you have code in the LostFocus/Valid of those controls or on the pages themselves that can disrupt the normal event processing?
>>>>
>>>>
>>>>>I believe it may be, except that in this case it happens after the user did the following:
>>>>>
>>>>>1. Enter text in textbox on page1
>>>>>2. Click on page2 tab
>>>>>3. Enter text in textbox on page2
>>>>>4. Click on save button on toolbar.
>>>>>
>>>>>Now when the focus is switched in step 2 above, then the valid should have fired and the control lost focus so the variable in the controlsource of the textbox on page1 should have the value entered in the textbox in step1 above, right? Even if the cursor never left the textbox until the user started typing in the textbox on page2 (in step3 above)...
>>>>>
>>>>>>Isn't this the same problem as a toolbar in general never receives the focus, so that your control never "leaves" so it hasn't done anything to store the change? You have to force your control to lose focus, so the LostFocus and/or Valid will kick in and store the value.
>>>>>>