Cancel Move To Next Record Problem 1

[GarstonMassive]

Hi,

I have a bound form which contains a number of bound controls inc txtDate and txtTime.

I'm trying to suppress the user moving to the next record if they only populate either txtDate or txtTime and not both of them.

The closest I've got is to test the Dirty event on the Form BeforeUpdate event, which works, but doesn't stop the user moving to the next record.

And I thought this one would be simple!

Has anyone got any (elegant) ideas?

 

[GarstonMassive]

...and if it's any help it's a subform.

 

[missinglinq]

How do your users move to the next record? Do they use the native navigation buttons or do you have custom buttons? With custom buttons you could check these two fields prior to moving to the next record.

The Missinglinq

There's ALWAYS more than one way to skin a cat!

 

[GarstonMassive]

...using the navigation buttons unfortunately. (not my system).

 

[PHV]

In the form's BeforeUpdate event procedure play with the Cancel argument and the SetFocus method if either txtDate or txtTime is invalid.

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886

 

[GarstonMassive]

Fantastic! Knew it would be something as simple as that.

And the good thing is - it works with subforms and main forms as well.

Thanks all.

 

[missinglinq]

...using the navigation buttons unfortunately. (not my system).

I'm confused (not that that's unusual) but you speak of changing code to prevent moving to another record without conditions being met, then you sound as if you cannot make changes to the form, because it's "not my system." If it were me, and I could, I'd do away with the native nav controls and place my own on the form. This makes checking the text boxes for data easy to do. I've tried the BeforeUpdate method before, and the problem I ran into was that while Access will process your code, it does so rather late! By that, I mean if you use BeforeUpdate to popup a messagebox telling users that they've left a textbox empty, it will, indeed, popup, but only after you've moved to another record or closed the form! Not much help there!

The good thing about using custom nav buttons is that you can not only add code behind them to check on the status of the text boxes, you can actually prevent the user from moving to another record or exiting the form by using the Dirty event:

Private Sub Form_Dirty(Cancel As Integer)
    MoveToFirstRecord.Enabled = False
    MoveToLastRecord.Enabled = False
    MoveToNextRecord.Enabled = False
    MoveToPreviousRecord.Enabled = False
    ExitForm.Enables = False 
End Sub

Of course, you have to reset these to True after the addition/edit is either saved or dumped. The point is, custom nav buttons give you a whole lot more control!

The Missinglinq

Richmond, Virginia

There's ALWAYS more than one way to skin a cat!

 

[GarstonMassive]

Missinglinq I agree that custom nav buttons do indeed give me more control but as this is a legacy system that I've inherited I dont want to start introducing "new features" which could put the users noses out of joint!

I couldn't disagree more however re: putting code into the BeforeUpdate event; with the help of PHV I included the line:

Cancel = True

and this prevents it moving to the next record like a dream.

And thankfully there is always more than one way to skin a cat!