Access VBA questions!

[fjcunninghamjr]

Hi,
If I am in the right forum, could someone help with the code below? Trying to set a blinking field. The CANDATE is the control which when there is data will run the code, when empty does nothing.
The text box default background is White and the text is Black
Thanks, Frank

Private Sub Form_Timer()


If CANDATE.IsNotNull Then
If CANDATE.BackColor = vbWhite Then
CANDATE.BackColor = vbRed
CANDATE.ForeColor = vbWhite
Else


CANDATE.BackColor = vbWhite
CANDATE.ForeColor = vbBlack
End If
End If

[Micron]

re forum - "Access" is kind of general, but it doesn't seem to matter much here.

when empty does nothing.

With that code, it is not possible that it "does nothing" - it has to process one or the other. I don't see the need for the nested IF.

In words, if the candidate has no value, bg should be white, fc should be black. If there is a value, bg should be red and fc should be white?
Why would you set this on form timer? Code will run every interval and regardless of what the condition is, nothing will change unless the condition changes between intervals. I don't see this as being a blinking field. If you want a blinking field, perhaps describe that in those terms.
EDIT - if candidate is null no changes will happen. If a value was removed between intervals, whatever the properties were set to, they will stay that way.

[Welshgasman]

Start indenting your code correctly.

It will help you immensely later on when code gets bigger.

Also use the code tag # when you post code.

If CANDATE.IsNotNull Then
    If CANDATE.BackColor = vbWhite Then
        CANDATE.BackColor = vbRed
        CANDATE.ForeColor = vbWhite
    Else
        CANDATE.BackColor = vbWhite
        CANDATE.ForeColor = vbBlack
    End If
End If

Se how much easier that is to read, even just a few lines?

[moke123]

Have you tried conditional formatting?

[CJ_London]

I'm struggling to understand what help is required. Blinks too fast? blinks too slow? doesn't blink?

So far as I know a control does not have an .isNotNull property, so perhaps it is a compilation or runtime error? Alternatively if IsNotNull is is valid, then CANDATE is not a control but something else (activeX perhaps?) or perhaps we are not talking about VBA but .net or similar?

And a companion to the timer property is the timer interval property. No idea if that has been set and if so to what?

Frank - please provide more information

[Micron]

Yeah, but I just ignored all of that and banged out a few lines that maybe would have taken care of it. However, have held on to it for lack of response. Well, it is Sunday (at least it is here).
EDIT - Come to think of it, not much point in setting the forecolor of a control where IsNull would be True?
#2 if it becomes red and then the value is removed before the next cycle, it could stay red.