Form having Multiple List Box Selections with each saving to 1 table field

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • d8nicole8l8e
    New Member
    • Feb 2013
    • 2

    Form having Multiple List Box Selections with each saving to 1 table field

    Hi there: I saw a great response to what I need, but the code doesn't work for me.

    I am building an Access 2003 Form that has multiple List Boxes, each having up to (10) items and the List Box is set to allow multiple choices. I need the users to be able to select multiple items from each List Box AND fill in other fields, lastly saving the record to a single table.

    Example:

    List Box (Conditions 1) (has 5 choices of which up to all 5 can be selected)

    Same with List Box (Conditions 2, 3, & 4).

    Then the user needs to fill in a number of other fields and then use the command button to "Save Record".

    All the Fill-In fields are separate fields in the "Save To Record" Table BUT the List Boxes each have (1) field that needs to store all choices from each List Box. Example List Box Conditions 1 should store as Broken, Cracked, Scratched. etc....

    Can you help me figure this out?

    Thanks, Nikki
  • Rabbit
    Recognized Expert MVP
    • Jan 2007
    • 12517

    #2
    You should not store multiple values in one column like that. It breaks the rules of normalization and makes querying a lot more difficult later on.

    Comment

    • d8nicole8l8e
      New Member
      • Feb 2013
      • 2

      #3
      What The Customer Wants

      Thanks for your response, but that is what the customer wants and they had no intentions of future querying.

      Appreciate it though.

      Comment

      • Seth Schrock
        Recognized Expert Specialist
        • Dec 2010
        • 2965

        #4
        Are you storing multiple values in a single field our are you getting many records and selecting many values?

        Comment

        • Rabbit
          Recognized Expert MVP
          • Jan 2007
          • 12517

          #5
          My point is that each choice should be stored in its own row. It preserves the data and doesn't break normalization rules.

          The entire purpose of a database is to be able to query data from it. It makes no sense that the data would never be queried. That's like buying food and ever eating it. If they ever want to see the choices they selected, then you have queried the data.

          Comment

          Working...