Re: non selectable table values
- From: "meilani" <meilani@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 30 Mar 2005 13:27:01 -0800
Thanks Rick, those are great suggestions. However
(1) I don't think the validation rule would work in my case since the values
I need blocked are not all necessarily at the top of the list; meaning items
#1, 5, and 12 is what I want to prevent from being used.
I suppose I could change things around but that would be very tricky to do,
wouldn't it? Also, would this interfere with past record entries that used
these values?
For instance I have tbl_Main that is linked to tbl_Version. A txt_Code field
on my form (tbl_Main source) holds a generated value based on the Version
value (combo box) the user chose.
(2) You're 2nd suggestion wouldn't work b/c I DO need to be able to allow
edits to old records.
Maybe, I can't have it both ways...
"Rick B" wrote:
> I would probably use a validation rule to specify that the field cannot
> contain a value less than X.
>
> Or, change the query upon which that drop-down is based to only include
> current values. As long as they do not go into previous records and try to
> modify that field, they will not run into problems.
>
> Rick b
.
- Follow-Ups:
- Re: non selectable table values
- From: Rick B
- Re: non selectable table values
- From: Rick B
- Re: non selectable table values
- References:
- non selectable table values
- From: meilani
- Re: non selectable table values
- From: Rick B
- non selectable table values
- Prev by Date: Re: non selectable table values
- Next by Date: Re: non selectable table values
- Previous by thread: Re: non selectable table values
- Next by thread: Re: non selectable table values
- Index(es):
Relevant Pages
|