Re: Why does Autoexpand in combo box not work with accented characters?
- From: jimatch4@xxxxxxxxx
- Date: Thu, 29 Nov 2007 16:02:38 -0800 (PST)
David,
I saw your post by randon accident and thought I would comment.
Don't know that this is directly relevant to your issue but,
Keep in mind that IF your ComboBox is populated in its DataSource
property by a SQL SELECT or SELECT DISTINCT statement, then unallowed
characters may break the SQL query that provides the source population
to the list box. The election for the version of ANSI SQL may also
affect this as there is differerent behavior in different ANSI SQLs in
Access. On just this see KB824189, depending upon Access version of
course. If you are not using a query "behind" or for the DataSource,
this is probably not a problem.
I had an experiece where users decided to put character that were in
not allowed by SQL language as it applies to MS Access (i.e., not
standard alpha-numeric and the few allowed symbols) and that started
breaking queries. It was a curve ball. It was ugly. I was able to
quickly discover that they were doing this, but it was a mystery at
first and could have caused a lot of frustrating troubleshooting time.
Many SQL queries brok in the app due to this in a key table. Not
practical in this instance to validate.
JIm
.
- References:
- Why does Autoexpand in combo box not work with accented characters?
- From: David Anderson
- Re: Why does Autoexpand in combo box not work with accented characters?
- From: Linq Adams via AccessMonster.com
- Re: Why does Autoexpand in combo box not work with accented characters?
- From: David Anderson
- Why does Autoexpand in combo box not work with accented characters?
- Prev by Date: Re: Form-Level Validation Rules and Data*** View
- Next by Date: Timeout when applying a filter
- Previous by thread: Re: Why does Autoexpand in combo box not work with accented characters?
- Next by thread: Re: repetitive data entry form design
- Index(es):