Flashing label

[FJM]

I have a label (label279) on a form which becomes visible if a check box (NEWPART) is ticked.

This is the code against the Form's Current event


Private Sub Form_Current()
If Me.NEWPART = -1 Then
Me.Label279.Visible = True
Else
Me.Label279.Visible = False
End If
End Sub

This works fine.

Can the code be modified sso that not only does the label become visible but it also fl;ashes in some way so there is no doubt that the user is aware of the message

[RuralGuy]

Flashing on the screen has been known to invoke medical issues with some. Your code can be shortened to just: Me.Label279.Visible = Me.NEWPART

[CJ_London]

you can use the form timer event

set the timer interval to say 3000 (for 3 seconds)

in the form timer event put

Me.Label279.Visible = not Me.Label279.Visible

However agree with Allan - generally not considered a good idea

Better to make the label stand out - perhaps use a red background or something with the borders or font

[FJM]

Thanks to you both for your replies ----wasn't aware of the medical issue so I think I will go with your suggestion of bolder colours........................

[FJM]

I have put the Me.Label279.Visible = Me.NEWPARTcode on the Forms Current event but it has given me an unexpected problem.
On the form there is a command button which adds a n

ew part but when I click this I get a warning message.
I have attached a screen print .
The code behind the Add Record is

Private Sub Command50_Click()
On Error GoTo Command50_Click_Err

On Error Resume Next
DoCmd.GoToRecord , "", acNewRec
DoCmd.GoToControl "partnumber"
If (MacroError <> 0) Then
Beep
MsgBox MacroError.DESCRIPTION, vbOKOnly, ""
End If


Command50_Click_Exit:
Exit Sub

Command50_Click_Err:
MsgBox Error$
Resume Command50_Click_Exit

End Sub

Is there a way around ?

[RuralGuy]

I'm sorry but my eyes can't read the error message. Would you just type it in a post please?

[FJM]

Runtime error '94@
Invalid use of Null

If I click the "end" button on the warning message I can then simply go to the PARTNUMBER control and type in the new recoird details as normal.......

[RuralGuy]

Comment out the "On Error Resume Next" line and you should see something useful.

[FJM]

I have just done that so the code now looks like below.............it doesn't change anything. Still the same error message which I can end and then move to the ADD RECORD control. Have I mis-understood something ?
'------------------------------------------------------------
' Command50_Click
'
'------------------------------------------------------------
Private Sub Command50_Click()
On Error GoTo Command50_Click_Err

'On Error Resume Next'
DoCmd.GoToRecord , "", acNewRec
DoCmd.GoToControl "partnumber"
If (MacroError <> 0) Then
Beep
MsgBox MacroError.DESCRIPTION, vbOKOnly, ""
End If


Command50_Click_Exit:
Exit Sub

Command50_Click_Err:
MsgBox Error$
Resume Command50_Click_Exit

End Sub

[RuralGuy]

When you attempt to move to a different record for any reason, Access will attempt to save any current record data if the record is "Dirty". Is the record Dirty? Have you changed something?

[FJM]

To the best of my knowledge, other than the change I have just made with the code for you, nothing else has changed........

[RuralGuy]

How about a MsgBox showing the value of Dirty? That might tell us something. At this point we do not know where the Null is causing the error and what is Null.

[CJ_London]

to be clear - what is macroerror?

my understanding is you are running vba code but

The MacroError object does not contain information about run-time errors that occur when running Visual Basic for Applications (VBA) code.

[FJM]

I am sorry - I do not understand what you mean with your question......are you looking for me to do something else ?

[FJM]

I am sorry, I don't understand ......