Check for BeforeUpdate success..?

[thatguyNYC]

Hello--

I have a form that lets the user edit the values in a lookup table. The form is bound to a table and has one textbox on it. The record nav buttons are enabled. On the top half of the form, I have a listbox showing all the records in the table. The user can double-click the listbox to jump to that record via this code:

    Me.RecordsetClone.FindFirst "[cSalut] = '" & Trim(Nz(Me.lstSaluts)) & "'"
If Not Me.RecordsetClone.EOF Then Me.Bookmark = Me.RecordsetClone.Bookmark
Me.txtSalut.SetFocus

In the form's BeforeUpdate event, I check to see that the new textbox value isn't blank and isn't already in the table

    ' prevent user from changing value to one already in the list
If DCount("[cSalut]", "[Saluts]", "[cSalut] = '" & Trim$(Nz(Me.txtSalut)) & "'") > 0 Then
   MsgBox "That Salutation already exists."
   Cancel = -1
End If
 
    ' prevent a blank record
If Len(Trim$(Nz(Me.txtSalut))) = 0 Then
   MsgBox "The Salutation field cannot be blank."
   Cancel = -1
End If

The problem occurs in this way:
- The user edits a record by clearing the textbox;
- The user then double-clicks the listbox
- The BeforeUpdate fires, but the textbox is blank so it gets cancelled
- However, the DblClick code still finishes and I get a No Current Record error on the Recordset.Bookm ark line.

So I'm wondering if there's any way to tell whether or not BeforeUpdate failed.

Thoughts?

Thanks

[thatguyNYC]

Well, I've come up with a semi-solution.. For the time being, until something better comes along, I've got this in the listbox_DblClic k():

If Me.Dirty Then
   MsgBox "Please save your changes before double-clicking this listbox."
Else
   ' move the recordpointer...
End If

And in the BeforeUpdate I have both data checks.

It's not the greatest, but it works.

Thanks.

[nico5038]

I never rely on the BeforeUpdate event. It can be done, but you'll need to cancel the event when the entered data is invalid.
I always use two "standard" windows buttons [Cancel] and [Save].
Cancel does close the form without leaving "traces" and the Save button will hold the validation and only add/update when all's OK.

Getting the idea ?

Nic;o)