Oncurrent event too fast?

[Neutrino]

Hi, I'm a newbie and have a quick question. I have introduced an "Oncurrent event" in order to check if two textbox have the same value. My code does not work but when I go step by step it does!!! Do you think the code is too fast so that the form doesn't have enough time to refresh? Here is the simple code:

Private Sub Form_Current()

If Me.SumaDebe = Me.SumaHaber Then
MsgBox "ok", vbOKOnly
Else
MsgBox "error", vbOKOnly
End If

End Sub

Any ideas? Thanks

[ajetrumpet]

define STEP BY STEP

[RuralGuy]

Hi, I'm a newbie and have a quick question. I have introduced an "Oncurrent event" in order to check if two textbox have the same value. My code does not work but when I go step by step it does!!! Do you think the code is too fast so that the form doesn't have enough time to refresh? Here is the simple code:

Private Sub Form_Current()

If Me.SumaDebe = Me.SumaHaber Then
MsgBox "ok", vbOKOnly
Else
MsgBox "error", vbOKOnly
End If

End Sub

Any ideas? Thanks

Not a chance but are you aware that when the form loads you may get more than one CurrentEvent? How about if you simply use the navButtons and switch records? Does it work then?

[Neutrino]

Sorry ajetrumpet, by step by step I mean that I put a breakpoint F9 in the first line of the code "If Me.SumaDebe = Me.SumaHaber Then" then I go step by step by using F8 and I find that it works...weird!!

[Neutrino]

Not a chance but are you aware that when the form loads you may get more than one CurrentEvent? How about if you simply use the navButtons and switch records? Does it work then?

I am using the nav buttons to move through records and does not work.

[RuralGuy]

I am using the nav buttons to move through records and does not work.

In that case there is something else going on. I assume these are two Controls on your form. Are they both bound to fields in the RecordSource of the form? If not, what is the ControlSource of those two controls?

[ajetrumpet]

that's strange. I remember a while back I heard about something like this with message boxes, but I can't remember now.

I just tested the same thing with a continuous form and it works fine, both with using rec selectors and navs, or changing via mouse or TAB on the keyboard.

is this on a network?

have you tried using a new form to try and combat a corruption issue?

<edit>
It looks like you've intrigued us both. Try Ruralguy's first, he will probably cover the most common mistakes made, as I tend to stray right to the complex stuff.

[RuralGuy]

We'll see what the reply is but I'm guessing a Domain Function in one of the ControlSources.

[ajetrumpet]

We'll see what the reply is but I'm guessing a Domain Function in one of the ControlSources.

Would that be the reason for the code executing faster than the population of the value? I remember seeing that complaint somewhere, but couldn't remember the reason.

[RuralGuy]

I'm not certain how the Tasker works but Domain Functions take longer that controls bound to fields so right now that is my best guess. I'm surprised the OP has not responded yet.

[weekend00]

The OP is at lunch.

[RuralGuy]

Ahh...you're right, I'm hungry too.

[Neutrino]

In that case there is something else going on. I assume these are two Controls on your form. Are they both bound to fields in the RecordSource of the form? If not, what is the ControlSource of those two controls?

Sorry, I was at lunch. Both textbox are bound to a Subform that is embedded in this "Form". The textboxes get their value by adding records within the "Subform". So the answer is no, they are not bounded to recordSource of the form.

[RuralGuy]

Sorry, I was at lunch. Both textbox are bound to a Subform that is embedded in this "Form". The textboxes get their value by adding records within the "Subform". So the answer is no, they are not bounded to recordSource of the form.

You are *definately* fighting a timing issue with the Tasker within Access. To make it work as you have it you either need to reference the SubForm directly instead of waiting for Access to resolve all of the indirections or place the values on the MainForm yourself in code.

[Neutrino]

I'm not certain how the Tasker works but Domain Functions take longer that controls bound to fields so right now that is my best guess. I'm surprised the OP has not responded yet.

The Textboxes take a fraction of a second to calculate, so it seems that the "Oncurrent" event is faster and gets me "OK" all of the time. When I run it through the breakpoint F9 (and use F8 to go step by step), it seems that I'm giving it the extra time needed to refresh the textbox and gives the correct answer everytime. I'm thinking about putting some time of delay so that to give the Textbox time to "refresh"....but not sure how.