Dropdown Property

  • Thread starter Thread starter Steve
  • Start date Start date
S

Steve

It seems like when a combobox is first in the taborder and the DropDown
property is set to true, when the form opens the list appears below the
combobox detached from the combobox. The same thing happens in a main form
and a subform. Is there a cure for this problem?

Thanks!
 
Problem? What problem? It's doing precisely what you told it to do; it
gets focus when the form opens because you've put it first in the tab order,
and in opens the list because you've set DropDown to true.

If you don't want that, either change the DropDown property or move it in
the taborder.

If you want it to *seem* to be the first control (but you'll have to tab to
it, or click on it when the form opens), you can put a tiny (1 pixel x 1
pixel) unbound textbox on your form - the top-left corner is a good spot,
it's extremely difficult to see the control there - and set that as the
first entry in the taborder.

HTH,

Rob
 
Hello, Steve Santus.
Is there a cure for this problem?

I've seen it in previous versions of Access, but it's fixed in Access 2003
SP-1 -- possibly even before SP-1 was installed, but I never checked. I
believe it's a bug in the earlier versions, so I think you're stuck with it
until you upgrade.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.
 
Oops - that'll teach me to read the posting in detail. I missed the
"detached from the combobox" bit!

And it's not something I've ever seen, so I wasn't aware of it.

Thanks Gunny,

Rob
 
Gunny,

Thanks for responding!

I have Access 2003 without SP-1 and the problem exists there.

Any ideas on how to circumvent the bug? I need the combobox to be the
control that has the focus when the form opens.

Steve
 
Hi, Steve.
Any ideas on how to circumvent the bug?

It's been a few years since I addressed this issue, so my memory is rather
hazy. IIRC, even adjusting the tab order so that the combo box wasn't the
first item didn't help. Executing the Dropdown property on open is what
caused the problem. I tested various combinations of property settings and
VBA code for about half an hour before I decided that it just wasn't worth
my time to fix this problem, so we just lived with it because the rest of
the functionality of the form worked as designed.

I think you need to install MS Office 2003 SP-1 if you want to get rid of
this bug. On the plus side, after you install this service pack Access will
be even more stable, bound subforms work better, and you'll have the Import
Text Wizard working as it should, too.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.
 
Gunny,

If you put SendKeys "{F4}" in the Open event that seems to keep the list
attached to the combobox when the form opens. If you add this line of code
in the form's design view and then immediately go to form view, the list
will still appear detached. You heve to close the form and then from there
on the list will be attached.

BTW, I did not mean to imply I am using Access2003 on my current project. I
am using Access XP in 2000 mode on my current project. I have Access 2003
and when I saw your response, I tried a test with Access 2003. Regarding
SP-1, I like to not install the service packs. I find that most people I do
projects for do not install the service packs so by my not installing them I
feel more assured people will not experience problems due to difference in
service packs with the databases I give them.

Steve
 
Hi, Steve.
If you put SendKeys "{F4}" in the Open event that seems to keep the list
attached to the combobox when the form opens.

Thanks for that. I'll try it on a computer with an earlier version of
Access installed, as this one only has Access 2003 SP-1, so doesn't
experience the disembodied list problem.
Regarding SP-1, I like to not install the service packs. I find that most
people I do projects for do not install the service packs

I hear what you're saying, but most of those service packs provide plugs for
security holes these days, so ignoring these service packs leaves your and
your customer's computers vulnerable. And I know that a lot of small
businesses have computer-phobes running them that don't want to break what
already seems to be working, but if they installed Microsoft Office
successfully, it's not that much of a stretch to install the service packs,
too. And for those customers who bought their computers with the software
pre-installed and don't want to mess it up by configuring it themselves,
offer to install the service packs for them, both for their operating
systems and Microsoft Office, then set it up for automatic updates, too.
These customers are hiring you for your expertise, so offer it to them.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads


Back
Top