G
Gina
Hi.
Could I make sure somehow that, when a user clicks the NEXT button, and the
recordset has arrived at the end EOF, that the next button doesn't offer the
option of going to a new empty record.
For now a user triggers an error message saying that null values arn't
allowed (guess from table def)
If the user wants to specifically create a new record a NEW button should be
pressed. That way I can make sure that no nonsense is saved to the db.
Here's the (standard) code for the next button. would I need to add sth.
_______________________________________
Private Sub cmdNext_Click()
On Error GoTo Err_cmdNext_Click
DoCmd.GoToRecord , , acNext
Exit_cmdNext_Click:
Exit Sub
Err_cmdNext_Click:
MsgBox Err.Description
Resume Exit_cmdNext_Click
End Sub
________________________________________
Many thanks,
Gina
Could I make sure somehow that, when a user clicks the NEXT button, and the
recordset has arrived at the end EOF, that the next button doesn't offer the
option of going to a new empty record.
For now a user triggers an error message saying that null values arn't
allowed (guess from table def)
If the user wants to specifically create a new record a NEW button should be
pressed. That way I can make sure that no nonsense is saved to the db.
Here's the (standard) code for the next button. would I need to add sth.
_______________________________________
Private Sub cmdNext_Click()
On Error GoTo Err_cmdNext_Click
DoCmd.GoToRecord , , acNext
Exit_cmdNext_Click:
Exit Sub
Err_cmdNext_Click:
MsgBox Err.Description
Resume Exit_cmdNext_Click
End Sub
________________________________________
Many thanks,
Gina