Use a table to hold the list values, instead of a Value List.
That's the only simple way to guarantee integrity between the values, and
provide an easy, single update point for the list.
For more discussion about this, see:
Adding values to lookup tables
at:
http://allenbrowne.com/ser-27.html#ValueList
--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"de_ja" <de_ja@[EMAIL PROTECTED]
> wrote in message
news:a2397d41-976f-45d5-9137-53c2afa32b67@[EMAIL PROTECTED]
>
> Thanks for assisting me with my previous query.
>
> I have almost completed my access database. And now in the process of
> optimising it.
>
> When I first developped the database I had implemented the "List Box"
> option for some of the data input (by the user) and specified a range
> of inputs for some of the form "boxes".
>
> Now I have arranged my form to look pretty and am ready to use the
> database, but I want to implement some more "List Box" inputs,
> however,
>
> when I update the lookup with
>
> Display Control - List Box
>
> Row Source Type - Value List
>
> Row Source - option1;option2;option3
>
> The actual box in the form view is not updated and even the properties
> for that box does not show the data that should be there if it was a
> List Box.
>
> Please could someone confirm, if perhaps it is now possible for me to
> do this now in an almost completed database, or perhaps I am missing
> something silly.
|
