Enter key Help 1

[Walshie1987]

I have a form with a search box, when I enter criteria in the search box and click a seach button, the record that matches the criteria is displayed then the "Req received date" box is highlighted ready for me to enter info in.

All the above works fine but, when the record is open ready for me to input things like dates etc. I enter some info and hit the enter key, instead of jumping to the next box, the db reruns the search. All the "enter key behaviour" properties are set to default, so i'm confused!

I now have to "tab" through the boxes to be able to enter info in them.

 

[danvlas]

Any AutoKeys macro?
Any KeyPress, KeyDown, KeyUp event procedures?
Any AfterUpdate event that triggers the search?

You could seek the SearchButton_Click event procedure in code...

HTH


Daniel Vlas
Systems Consultant

http://www.geocities.com/danvlas/AutoMail.html

 

[TheAceMan1]

How are ya Walshie1987 . . .

You have [blue]code in some event that call or duplicates that of the buttton[/blue]. A quick scan of the forms module should reveal the culprit ([blue]perhaps code you copied instead of removing while testing![/blue])

See Ya! . . . . . .

 

[Walshie1987]

Yeah will check that, was working fine just isn't now. We did have a temp working for us last week who was also using the database. Maybe they changed the code trying to sort a problem ....without informing me! Not too sure though, will have to see

It's got to be something straight forward i'd have thought

Cheers for your replies

 

[missinglinq]

Yikes! To much access to the Access!

The Missinglinq

Richmond, Virginia

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

 

[Eupher]

Hiya, Walshie1987,

Check the "Default" property of your search command button. Normally, hitting the <Enter> key moves the cursor to the next control in the tab order. But if a command button has its "Default" property set to "Yes," hitting <Enter> anywhere on the form is just like clicking the mouse on the button.

HTH,

Ken S.

 

[Walshie1987]

Yep that sorted it, someone had changed the default property to yes I think I might make the db a bit more secure now!