COMBO BOX vs Uppercase

[fishqqq]

I have a combo box listing a column of City State in Upper & lower
case (for example "Los Angeles CA")
and the combox box works perfectly if the user has his keyboard set to
lower case.
If the user has his keyboard set to uppercase the combo box doesn't
work correctly and the user has to backspace then change to lowercase
format then start his search again.

I know this doesn't seem like a big deal but with hundreds of cities
in the dropdown box column and the users working very quickly to input
the data (which is our environment) it really slows things down and
breaks the users rhythem. Is there a way the users can set their
keyboards to uppercase and still have the dropdown boxes work
correctly? or would i have to reformat all the data to uppercase first
then the user will be able to use the dropdown box in uppercase
mode???


Tks
Steve

 

[John W. Vinson]

I have a combo box listing a column of City State in Upper & lower
case (for example "Los Angeles CA")
and the combox box works perfectly if the user has his keyboard set to
lower case.
If the user has his keyboard set to uppercase the combo box doesn't
work correctly and the user has to backspace then change to lowercase
format then start his search again.

I know this doesn't seem like a big deal but with hundreds of cities
in the dropdown box column and the users working very quickly to input
the data (which is our environment) it really slows things down and
breaks the users rhythem. Is there a way the users can set their
keyboards to uppercase and still have the dropdown boxes work
correctly? or would i have to reformat all the data to uppercase first
then the user will be able to use the dropdown box in uppercase
mode???


Tks
Steve

I haven't seen this phenomenon! Access searches are not case sensitive, nor
are combo boxes. What is the RowSource property of the combo box? What is the
datatype of the table field you're using as the Control Source? In which way
does it "not work correctly"?
--

John W. Vinson [MVP]
Microsoft's replacements for these newsgroups:
http://social.msdn.microsoft.com/Forums/en-US/accessdev/
http://social.answers.microsoft.com/Forums/en-US/addbuz/
and see also http://www.utteraccess.com

 

[fishqqq]

I haven't seen this phenomenon! Access searches are not case sensitive, nor
are combo boxes. What is the RowSource property of the combo box? What isthe
datatype of the table field you're using as the Control Source? In which way
does it "not work correctly"?
--

             John W. Vinson [MVP]
 Microsoft's replacements for these newsgroups:
 http://social.msdn.microsoft.com/Forums/en-US/accessdev/
 http://social.answers.microsoft.com/Forums/en-US/addbuz/
 and see alsohttp://www.utteraccess.com

the RowSource propert of the combo box is :
SELECT DISTINCTROW [All Points Q].[Full Point] FROM [All Points Q];

The data type is [Text]

here's what happens

the underlay data is in the table as follows:
Toronto ON (not TORONTO ON)

If the user has his keyboard set in lower case then as be begins
typing in the field [Origin] the word Toronto begins to be found
If the user has his keboard set to uppercase then as be begins typing
the word TORONTO in the field [Origin], the field begins to update as
follows: ToRamasina Madagascar (note Toamasina Madagascar is the next
origin in the list after the word Toronto)

what's happening is a capital TOR is entered by the user and the sys
updates this to ToR (then continues to find the word in the list and
comes back with ToRamasina Madagascar ).

it would be great if the user could type in upper or lower case and
the field would update accordingly

is there anything I can set to correct this?

tks
Steve

 

[fishqqq]

I haven't seen this phenomenon! Access searches are not case sensitive,nor
are combo boxes. What is the RowSource property of the combo box? What is the
datatype of the table field you're using as the Control Source? In which way
does it "not work correctly"?
--

             John W. Vinson [MVP]
 Microsoft's replacements for these newsgroups:
 http://social.msdn.microsoft.com/Forums/en-US/accessdev/
 http://social.answers.microsoft.com/Forums/en-US/addbuz/
 and see alsohttp://www.utteraccess.com

the RowSource propert of the combo box is :
SELECT DISTINCTROW [All Points Q].[Full Point] FROM [All Points Q];

The data type is [Text]

here's what happens

the underlay data is in the table as follows:
Toronto ON  (not TORONTO ON)

If the user has his keyboard set in lower case then as be begins
typing in the field [Origin] the word Toronto begins to be found
If the user has his keboard set to uppercase then as be begins typing
the word TORONTO in the field [Origin], the field begins to update as
follows: ToRamasina Madagascar (note Toamasina Madagascar is the next
origin in the list after the word Toronto)

what's happening is a capital TOR is entered by the user and the sys
updates this to ToR (then continues to find the word in the list and
comes back with ToRamasina Madagascar ).

it would be great if the user could type in upper or lower case and
the field would update accordingly

is there anything I can set to correct this?

tks
Steve

I should also mention that an industry requirement we are prevented
from working totally in uppercase (we need our data to be in upper/
lower case format) - otherwise would just convert all the data in our
dbase to uppercase and fix this problem that way)

 

[Douglas J Steele]

I believe you need your combo box to be sorted for it to work.

Try changing your RowSource to

SELECT DISTINCTROW [All Points Q].[Full Point] FROM [All Points Q] ORDER BY
1


wrote in message

On Oct 1, 7:17 pm, John W. Vinson <jvinson@STOP_SPAM.WysardOfInfo.com>
wrote:

the RowSource propert of the combo box is :
SELECT DISTINCTROW [All Points Q].[Full Point] FROM [All Points Q];

The data type is [Text]

here's what happens

the underlay data is in the table as follows:
Toronto ON (not TORONTO ON)

If the user has his keyboard set in lower case then as be begins
typing in the field [Origin] the word Toronto begins to be found
If the user has his keboard set to uppercase then as be begins typing
the word TORONTO in the field [Origin], the field begins to update as
follows: ToRamasina Madagascar (note Toamasina Madagascar is the next
origin in the list after the word Toronto)

what's happening is a capital TOR is entered by the user and the sys
updates this to ToR (then continues to find the word in the list and
comes back with ToRamasina Madagascar ).

it would be great if the user could type in upper or lower case and
the field would update accordingly

is there anything I can set to correct this?

tks
Steve

 

[fishqqq]

I believe you need your combo box to be sorted for it to work.

Try changing your RowSource to

SELECT DISTINCTROW [All Points Q].[Full Point] FROM [All Points Q] ORDER BY
1

wrote in message
On Oct 1, 7:17 pm, John W. Vinson <jvinson@STOP_SPAM.WysardOfInfo.com>
wrote:

the RowSource propert of the combo box is :
SELECT DISTINCTROW [All Points Q].[Full Point] FROM [All Points Q];

The data type is [Text]

here's what happens

the underlay data is in the table as follows:
Toronto ON  (not TORONTO ON)

If the user has his keyboard set in lower case then as be begins
typing in the field [Origin] the word Toronto begins to be found
If the user has his keboard set to uppercase then as be begins typing
the word TORONTO in the field [Origin], the field begins to update as
follows: ToRamasina Madagascar (note Toamasina Madagascar is the next
origin in the list after the word Toronto)

what's happening is a capital TOR is entered by the user and the sys
updates this to ToR (then continues to find the word in the list and
comes back with ToRamasina Madagascar ).

it would be great if the user could type in upper or lower case and
the field would update accordingly

is there anything I can set to correct this?

tks
Steve

SELECT DISTINCTROW [All Points Q].[Full Point] FROM [All Points Q]
ORDER BY
1 gives me the same result. If the keybord is in uppercase then it
doesn't search properly.

any other suggestions?
tks
Steve

 

[David-W-Fenton]

:

SELECT DISTINCTROW [All Points Q].[Full Point] FROM [All Points Q]
ORDER BY 1

I'd get rid of DISTINCTROW in favor of DISTINCT, given that the
combo box is not editable, and there's only one table in the FROM
clause.