LostFocus event....

[ItIsHardToProgram]

I have a function that checks for a boolean variable and if that variable is set to false, it needs to cancel the losing focus event, and reset focus. so what I did is a simple if, with a msgbox and if it is false then
Forms![Feuille_Temps_F1]![SelSem].SetFocus

Unfortunatly that does not stop the user from losing focus, why??? (it does not setfocus back on the combo box.)

I tried a cancelevent also, still no effect....

 

[Eupher]

Use the Exit event instead, then you can use the Cancel argument (Exit event has Cancel, LostFocus does not).

HTH,

Ken S.

 

[ItIsHardToProgram]

Thanks, your right, I dint notice the Exit event, another question regarding a related issue, is there a way of preventing the record from being written down (bound txtboxes) if some of the fields were not filled? (prevent errors in database.)

I would like to evade the recordset :/

 

[Eupher]

Probably the simplest way is to edit the table in design view and set the "required" property on the fields in question to "yes."

Otherwise you could use the form's BeforeUpdate event to validate your data and use either Cancel or Undo to prevent bad or null data being written.

Ken S.

 

[TheAceMan1]

[blue] . . . is there a way of preventing the record from being written down (bound txtboxes) if some of the fields were not filled?[/blue]

You'll have to use your own [blue]Validation Scheme[/blue] in the [blue]BeforeUpdate[/blue] event of the form . . .

See Ya! . . . . . .

 

[ItIsHardToProgram]

Thanks TheAceMan1 that would do it.

 

[ItIsHardToProgram]

Just one last question, doesnt every field write down seperatly in the table, and so I would have to put a validation scheme in every single beforeupdate of my form, or would passing through a delete request on the close event of the form be a good work around.

 

[TheAceMan1]

[blue] . . . doesnt every field write down seperatly in the table, and so I would have to put a validation scheme in every single beforeupdate of my form[/blue]

Wrong Idea! . . .
1st . . . a record isn't saved until you:
[ol][li]Move to a different record.[/li]
[li]Save a record thru VBA.[/li]
[li]Close the form.[/li][/ol]
For a record to be saved it has to be in edit mode (depicted by the pencil icon in the record selector). Edit mode is triggered when you start editing a record.

With the above in mind,the [blue]Before/AfterUpDate[/blue] events of a field occur [purple]in relation to updating the field[/purple] (not saving). The [blue]Before/AfterUpDate[/blue] events of the form [purple]occur in relation to saving the record[/purple].

So you can check all fields in the forms BeforeUpdate event! . . . If a field doesn't pass validation you can use the [blue]Cancel[/blue] arguement to roll back saving.

See Ya! . . . . . .