There are a lot of times that the Value of a textbox is different from its underlying ControlSource. If the control has the focus and the Value is updated, either programmatically or interactively, the Control's Value has not been run through the Valid() method and could be different, even invalid, without affecting the ControlSource. This is a feature, not a bug, we use in InteractiveChange() or ProgrammaticChange() to react to changes in Value without affecting the underlying data. Then, there's the whole discussion of buffering.
So, perhaps you can tell us a little bit more of the context of when this happens. If you can't reproduce it in a simple example, then it is something with your code, environment or framework, and that's kinda hard for us to guess. On Tue, Dec 17, 2019 at 5:34 AM MB Software Solutions, LLC < [email protected]> wrote: > See https://www.screencast.com/t/mQEK40Tqp. > > I don't understand how the thisform.txtDraftingRate.Value is not equal > to 1 as well? Causing a bug in my code at the moment. > > tia, > --Michael > > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/cacw6n4uwkc0+wvkq_adb5jy339f_nbjw7cmpn0-ath+w0ph...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
