ComboBox property "Auto Expand", the combobox doesn't open by typing

[Simon van Beek]

Dear reader,

What can be wrong in my ComboBox, the property "Auto Expand" is set to Yes,
but by typing in the ComboBox it doesn't expand. Is this because the source
of the ComboBox is a query.

Tanks for any help.

Kind regards,

Simon

[fredg]

On Fri, 31 Oct 2008 23:00:52 +0100, Simon van Beek wrote:

Dear reader,

What can be wrong in my ComboBox, the property "Auto Expand" is set to Yes,
but by typing in the ComboBox it doesn't expand. Is this because the source
of the ComboBox is a query.

Tanks for any help.

Kind regards,

Simon

Your Subject line and message body appears to conflict.

What do you mean by "doesn't open by typing" and by "doesn't Expand"?

Are you expecting the combo box to drop-down when you type so that you
can see all the possible values?
AutoExpand does not do that.

With AutoExpand set to Yes, the combo box, as you type in data, will
find the next available data that begins with the values you have
already typed. For example, if you have a list of names, one of which
is Sandler and one is Smith, as you enter the 'S', Sandler will
appear. Next type the 'm' and Smith will appear. That is AutoExpand.

If you mean the combo doesn't drop-down to show the possible values
available, that is "Drop-Down". A combo will only drop-down when you
click on the down arrow OR if you have used code to tell it to do so.
For instance, you can code the Combo Box's Enter event:

Me.[ComboName].Dropdown

--
Fred
Please respond only to this newsgroup.
I do not reply to personal e-mail

[Simon van Beek]

Fred,

What I need is that by typing in the combo box the next available data will
be appear.

The property AutoExpand is set Yes but by typing the combo box will not go
to the character combination I type and I know that the typed combination
exist.
Thanks for any help,
Simon
"fredg" <fg******@examp le.invalidwrote in message
news:zn******** *************** *******@40tude. net...

On Fri, 31 Oct 2008 23:00:52 +0100, Simon van Beek wrote:

>Dear reader,

What can be wrong in my ComboBox, the property "Auto Expand" is set to
Yes,
but by typing in the ComboBox it doesn't expand. Is this because the
source
of the ComboBox is a query.

Tanks for any help.

Kind regards,

Simon

Your Subject line and message body appears to conflict.

What do you mean by "doesn't open by typing" and by "doesn't Expand"?

Are you expecting the combo box to drop-down when you type so that you
can see all the possible values?
AutoExpand does not do that.

With AutoExpand set to Yes, the combo box, as you type in data, will
find the next available data that begins with the values you have
already typed. For example, if you have a list of names, one of which
is Sandler and one is Smith, as you enter the 'S', Sandler will
appear. Next type the 'm' and Smith will appear. That is AutoExpand.

If you mean the combo doesn't drop-down to show the possible values
available, that is "Drop-Down". A combo will only drop-down when you
click on the down arrow OR if you have used code to tell it to do so.
For instance, you can code the Combo Box's Enter event:

Me.[ComboName].Dropdown

--
Fred
Please respond only to this newsgroup.
I do not reply to personal e-mail

[Robert S.]

Hello Simon,

Simon van Beek wrote:

What I need is that by typing in the combo box the next available data will
be appear.

The property AutoExpand is set Yes but by typing the combo box will not go
to the character combination I type and I know that the typed combination
exist.

is it the case, that you are using Access 2007 with a database
originally designed unter Acc2000?

I stumbled over your post because having a very strange behaviour with a
comboboxes, myself.

Some minutes ago I verified behaviour in a VM under XP with Acc2000
running. There my dialog EXACTLY does what it should. When typing a
letter it jumps to the first entry to be found in the list. However,
when running under Vista/Acc2007 it does not automatically select the
first entry in list as it does in Acc2000.

I read deeper into Acc2007 docs (I am not very pleased of the new help
system - nearly no samples anymore - what funster did throw that things
out?) but could not find any additional switch/property to reenable things.

I did not try this behavio under a plain 2007 designed form, yet, but I
am very close to believe it is a nasty bug with 2000 designed forms.
Ok. I should go into more details, so maybe - if some MS folks are
reading along and interested into this - can understand what is going on
and maybe could find a fix for this (or not. Sorry dudes for sarcasm).

This solution (yes it is part of a bigger development) has been
originally designed under XP/Acc2000. I did not convert this project
into a 2007 'database' program (because customers still using old
ms-ffice. Most of em 2k some 2k3. And as we all know there are ugly side
effects pending prevent a side by side install).

In a form there is a combobox and as datasource I do use a SELECT tbl
anything statement. Using two columns as recordsource, where only the
last one is shown. First column I use to get back a value-ID (column
size = 0 does hide column away during runtime). This field is unbound.

In event 'AfterUpdate' I do open another form. This doing nothing else
than waiting for some user input, so no other automatism can break anything.

As I defined in properties of the combobox LimitToList=tru e, MS Access
throws a message telling that value is not in list. This actually
happens if writing a complete entry to be found in list. It simply does
not position to this list value. It seems as Access2007 tries to focus
on column ONE! not visible and not as to be expected on column two!!!

In Access 2000 I know that for some strange reasons filters on
comboboxes try to grab the first hidden fields, sometimes. I never could
reproduce this behaviour. So I expect that there is a similar problem in
Access2007, here, too. (Maybe for compatibility - who knows...;)

Ok folks, hoping that there are already solutions out for this problem?
rob*