A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Using Forms
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

LimitToList Property isn't working



 
 
Thread Tools Display Modes
  #1  
Old September 24th, 2004, 10:23 PM
Luther
external usenet poster
 
Posts: n/a
Default LimitToList Property isn't working

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.
  #2  
Old September 25th, 2004, 05:21 AM
Dirk Goldgar
external usenet poster
 
Posts: n/a
Default

"Luther" wrote in message

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.


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?

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)


  #3  
Old September 27th, 2004, 02:45 PM
Luther
external usenet poster
 
Posts: n/a
Default

Thank you for responding. To answer your questions, the
properties a

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.

-----Original Message-----
"Luther" wrote in

message

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.


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?

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)


.

  #4  
Old September 27th, 2004, 05:01 PM
Dirk Goldgar
external usenet poster
 
Posts: n/a
Default

"Luther" wrote in message

Thank you for responding. To answer your questions, the
properties a

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.

-----Original Message-----
"Luther" wrote in message

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.


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?


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.

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)


  #5  
Old September 27th, 2004, 08:40 PM
Luther
external usenet poster
 
Posts: n/a
Default

Thanks, Dirk. I have just sent you the sample you
requested. Hope that the solution is easily apparent...

-----Original Message-----
"Luther" wrote in

message

Thank you for responding. To answer your questions, the
properties a

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.

-----Original Message-----
"Luther" wrote

in message

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.

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?


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.

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)


.

  #6  
Old September 27th, 2004, 09:16 PM
Dirk Goldgar
external usenet poster
 
Posts: n/a
Default

"Luther" wrote in message

Thanks, Dirk. I have just sent you the sample you
requested. Hope that the solution is easily apparent...

-----Original Message-----
"Luther" wrote in message

Thank you for responding. To answer your questions, the
properties a

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.

-----Original Message-----
"Luther" wrote in message

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.

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?


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.


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.

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)


 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Outlook 2003 Junk Filter not working Rayd8tor General Discussions 2 June 17th, 2004 10:31 PM
Changing field indexed property from code Christopher Database Design 0 June 11th, 2004 03:17 PM
Formula Property - Referencing Strings Inside Formula Property Value Oak Worksheet Functions 8 February 10th, 2004 11:54 AM


All times are GMT +1. The time now is 07:08 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.