LimitToList Property isn't working

  • Thread starter Thread starter Luther
  • Start date Start date
L

Luther

Hello,

I have a combo box with the following SQL RowSource
attached to it:

SELECT tblSource.Year & tblSource.SourceValue AS
SourceCode FROM tblSource WHERE (((tblSource.Year)="03"));

This works fine as far as displaying what I need, but even
though I have set the Limit To List property to "Yes", it
still allows other values to be entered. What am I doing
wrong?

Any help would be greatly appreciated.
 
Luther said:
Hello,

I have a combo box with the following SQL RowSource
attached to it:

SELECT tblSource.Year & tblSource.SourceValue AS
SourceCode FROM tblSource WHERE (((tblSource.Year)="03"));

This works fine as far as displaying what I need, but even
though I have set the Limit To List property to "Yes", it
still allows other values to be entered. What am I doing
wrong?

Any help would be greatly appreciated.
Click to expand...

I've never heard of LimitToList not firing properly before. What are
the values of the following properties of the combo box, from its
property sheet in design view:

Column Count
Bound Column
On Not In List

?

If there's an event procedure for the NotInList event, what is the code?

You're saying that you can type a value into the combo box that isn't in
the list, and it makes no complaint at all?
 
Thank you for responding. To answer your questions, the
properties are:

Column Count=1
Bound Column=1
On Not In List = nothing entered there

One thing, though, this happens to existing data that is
being edited; for example, there are 4 pre-existing
fields: Source1, Source2, Source3, Source4. They have data
from previous years in them; not all fields are filled in.

Source1=02A
Source2=blank
Source3=blank
Source4=blank

The user will need to update Source2 with this year's
data, and end up with something like this:

Source1=02A
Source2=04G
Source3=blank
Source4=blank

Source2 is an example of the field I'm trying to limit.

Thanks for your attention.
 
Luther said:
Thank you for responding. To answer your questions, the
properties are:

Column Count=1
Bound Column=1
On Not In List = nothing entered there

One thing, though, this happens to existing data that is
being edited; for example, there are 4 pre-existing
fields: Source1, Source2, Source3, Source4. They have data
from previous years in them; not all fields are filled in.

Source1=02A
Source2=blank
Source3=blank
Source4=blank

The user will need to update Source2 with this year's
data, and end up with something like this:

Source1=02A
Source2=04G
Source3=blank
Source4=blank

Source2 is an example of the field I'm trying to limit.

Thanks for your attention.
Click to expand...

I'm having trouble figuring out how this is set up. Would you be
interested in making a cut-down copy of your database, containing only
the elements necessary to demonstrate the problem? If so, please be
sure to remove all non-essentials, then compact it and, by preference
use a zip utility to compress it to less than 1MB in size (preferably
much smaller). I'll have a look at it, time permitting. You can send
it to the address derived by removing NO SPAM from the reply address of
this message.
 
Thanks, Dirk. I have just sent you the sample you
requested. Hope that the solution is easily apparent...
 
Luther said:
Thanks, Dirk. I have just sent you the sample you
requested. Hope that the solution is easily apparent...
Click to expand...

Um, Luther, the LimitToList property is set to No for your combo boxes
Source2, Source3, and Source4. It's Yes for the rest of them, but not
for those three.

As a side note, any table that has fields named Source1, Source2,
Source3, ... Source10 could probably benefit from having those fields
moved out into a separate, related table, wherein each source code would
be a row, rather than a column.
 
Back
Top