Form Gets Stuck on Records

  • Thread starter Thread starter MT DOJ Help Desk
  • Start date Start date
M

MT DOJ Help Desk

Access 97

I have a form with a number of fields. One of the fields is a Yes/No data
type. If the cursor is above the Yes/No field I cannot move to other
records. If I put the cursor on, or below, the Yes/No field, I can move to
any record that I want. The Yes/No field is a checkbox control, it is not
required or indexed, and has no validation rule. What would cause this, and
how do I fix it?

--Tom
 
---------- "MT DOJ Help Desk said:
Access 97

I have a form with a number of fields. One of the fields is a Yes/No data
type. If the cursor is above the Yes/No field I cannot move to other
records. If I put the cursor on, or below, the Yes/No field, I can move to
any record that I want. The Yes/No field is a checkbox control, it is not
required or indexed, and has no validation rule. What would cause this, and
how do I fix it?

Tom,

how would you move to another record? Navigation buttons?
And what does it mean "cursor is above the Yes/No field"? Does the
check box have the focus or is the cursor actually "geographically" in
some control above the check box? Or do you mean just swaying with the
mouse over it?

Is there some error message, some other strange behaviour?

Best regards
Emilia

Emilia Maxim
PC-SoftwareService, Stuttgart
http://www.maxim-software-service.de
 
I've solved the problem. The reason I was not able to move to another
record when certain fields on the form had the focus is that those fields
had an On Exit event procedure that simply converted the field contents into
upper case. The event procedure didn't cause any problems as long as I
tabbed from field to field, but for some reason, it was preventing me from
moving to other records by clicking on the navigation buttons. This was a
little difficult to work out because only the fields that had the On Exit
event procedure would cause a problem, and only if they contained a value
(Empty fields with the On Exit event procedure weren't a problem). So it
was a little hard to see the common thread between the fields on the form.

I changed all the On Exit event procedures to After Update event procedures,
and now everything works fine.

Just out of curiosity, why would the On Exit event procedure cause this
behavior?

--Tom
 
Just out of curiosity, why would the On Exit event procedure cause this
behavior?

Good debugging job... that was a tough one!

Exit fires when the control gets the focus, and then loses it. If the
control never actually gets the focus - as will happen when you bring
up a record, don't touch that particular control, and then navigate to
another record - the Exit event will never fire.
 
Back
Top