How can you use down arrow key to scroll in a drop box?

[DanicaDear]

I have a QTY field and an ITEM field. User inputs a number into the QTY field, then tabs over the the next field and there's a down arrow on the right hand side of the field that you click to choose the correct item from the drop box. The combination of the QTY and the ITEM is the primary key (two primary keys). When I tab over to the ITEM field and press the down arrow, a message box pops up telling me that a primary key field can't be null (I suppose it's trying to go down to the next box rather than going through the drop down items). Is there an easy fix for this? I want to hit TAB key, DOWN KEY (multiple times to get through the drop box), TAB key (to get to the next QTY field). Thanks!!

Missed you Bytes friends. Implementing the new DB...will be back in January with my next one. :-)

[Delerna]

Hmm .... I think you might need to code that functionality into the "key down" event of the combo box in VBA.

I could thow something together for you if you like. I encourage you to try it for youself first, though.

[missinglinq]

I can only replicate your problem by entering a QTY, tabbing into the Item Combobox, then Tabbing again, which is, as you said, trying to go to the next control. If you tab into the Combobox and use the mouse to drop down the box, everything works fine.

What I'd do, simply to decrease the chance of hitting Tab twice and popping the error, would be to automatically drop down the box when entering it:

Private Sub ItemComboBoxName_GotFocus()
 ItemComboBoxName.Dropdown
End Sub

Linq ;0)>

[DanicaDear]

Ok, I was going to take Delerna's approach and try to come up with something myself....but I figured I was going to have to ask for a hint. Do you just need a good VBA book to learn what GotFocus() means, for example? My Access book has a chapter on VBA....but I'd need a listing of all the commands.... something more in depth.

I haven't had a chance to try your idea Linq but it looks like that is the exact direction I want to go.

[missinglinq]

Here's a couple of sites that go into VBA:.

Chrystal has an excellent “basics” tutorial:

http://www.accessmvp.com/strive4peace

Jeff Conrad's resources page:

http://www.accessmvp.com/JConrad/acc...resources.html

Linq ;0)>

[Delerna]

Just a word of advice using got focus and lost focus events.

Take care because your code can quite easily be sent crazy bouncing around the various got and lost focus handlers of your controls.

Got focus of control1 and code in there causes control2 to get focus which cause lost focus of control1 to fire and code in got focus of control2 causes control1 to get focus.so got focus of control1 fires again as well lost focus of control2.

It quickly becomes quite hairy.
Try hard to use other events instead of got and lost focus wherever you can

[missinglinq]

Take care because your code can quite easily be sent crazy bouncing around the various got and lost focus handlers of your controls....

Got focus of control1 and code in there causes control2 to get focus

I'm sorry, but the code can't be sent bouncing any crazier than the scenario you presented! What possible reason would anyone have to place code in control1_GotFoc us to send the focus to control2, as you suggest?

All events have to be used properly, paying attention to when they fire and exactly what triggers them, but making a statement like this about GotFocus and LostFocus is simply inane and gives a totally false impression!

Linq ;0)>

[Delerna]

I was merely trying to illustrate a point and chose an over the top example to illustrate it.

I have had experience debugging a database written by a colleague who found many inventive ways to use got and lost focus for many controls on the same form. The problem was that code written in other events caused the mentioned events to fire in unexpected ways, unexpected to my colleague that is, due to his inexperience at writing software. Indeed, I myself suffered the same experience when starting out. I found that inappropriate use of those 2 events in particular more troublesome, more difficult to get my mind around, more difficult to debug than any other.

I certainly do not wish to give a false impression, just sharing my observations.
Having said that,
it certainly is true that

All events have to be used properly, paying attention to when they fire and exactly what triggers them

[DanicaDear]

As always, thanks for the thorough explanations. I'm always appreciative. I haven't grasped the whole GotFocus concept yet but I'm working on it. (I've been away from Access for awhile...which is not smart for me!)

Moving on....I got the GotFocus and .Dropdown as referenced above to work in the form. However, the form is a subform used on another form. It wouldn't work in the main form. (It just behaved as if the code weren't there at all, and the original problem is still my problem.) Any ideas why it works on the subform when it is opened all alone and not on the mainform that contains it?
Thanks in advance!
Danica

[Delerna]

Hi Dancia
Have you tried putting breakpoints on the events coded in both the main form and the subform and then running your form and making the change. That way you can trace throught the sequence of events looking to see if things are happening as you expected. It is also a good method to learn which events fire and in what sequence they fire. Keep in mind that when your code stops at a breakpoint, you can hover your mouse pointer over variables and see their contents.

Breakpoints are also great for examining how a piece of code works even when there are no errors.
Just breakpoint every line of the code you want to examine, and the cause it to execute.
You can then watch the execution of the code, hover over variables/objects at each step and see how the code is changing them and all manner of useful things.
You can even drag the execution point to a different line,
change code on the fly, the list goes on and on.

Effective use of the debugger is the primary tool that will enable you to answer your own questions.....n ot that I am trying to discourage you from asking questions here.


Anyway, you will need to post the piece of code that you believe is at fault along with a clear desciption of what is happening.
I assume that

the original problem is still my problem

means

a message box pops up telling me that a primary key field can't be null

but you know what happens when you assume things.
My initial thought is that you are trying to move focus from the main form to the subform but a key field on the main form has not been filled in, but I am just guessing