multiple options in 1 cell

[gdm]

I have a 2 tables

Table A = Master
Table B = information that's referenced into Table A

The reason for Table B is because information in here can
be added to or deleted.

Right now I have 7 options in Table B. Well I want to
make all 7 option 1 cell in Table A.

Currently I have 7 cells for each option which I don't
want. Can I make it so all 7 options are in one Cell?
All the options are pull downs.

TIA!!

 

[Pavel Romashkin]

If you have 7 option groups, such as Color [Red, Green, Blue], Size [S,
M, L, XL], Category [Mens, Womens, Childrens] then don't make these into
a single field because it will become very difficult later to do
searches and filtering of the database. Use each of the option group as
the lookup source in Table B, which is a Many side of a One-Many
relationship with Table A.
If you have one option group, you should have options as records (rows)
in one table, and use it as the lookup for the Option field of the
Master table.

Pavel

 

[Evi]

Pavel is correct, I have nearly always regretted combining data fields. But
if you want it to LOOK as if its in one field then in your queries (and thus
your reports you could put

Details: [Color] & ", " & [Size] & ", " & [Category]

In the query you will get a field that says

Red, S, Mens

(You can omit the comma if you just want a space between the fields.)

If you really only have two tables then you actually need some extra tables
in your database if you want a real relational database.

TblColor contains all 1 ID field and the colour names

TblSize contains 1 ID field and the different sizes
TblCategory contains 1 ID field the different categories.

Your main table, TblGarment would contain eg

Garment, ColorID, SizeID, CategoryID and then any fields that apply only to
that garment eg Price

A form based on TblGarment would have combo boxes with look up the data in
those those other tables and Store the data in the respective ID field (it
looks up ColorID and Color in TblColor and stores its data in ColorID in the
form.)

I don't know why you need a table that lets you add or delete data.

Evi

If you have 7 option groups, such as Color [Red, Green, Blue], Size [S,
M, L, XL], Category [Mens, Womens, Childrens] then don't make these into
a single field because it will become very difficult later to do
searches and filtering of the database. Use each of the option group as
the lookup source in Table B, which is a Many side of a One-Many
relationship with Table A.
If you have one option group, you should have options as records (rows)
in one table, and use it as the lookup for the Option field of the
Master table.

Pavel

I have a 2 tables

Table A = Master
Table B = information that's referenced into Table A

The reason for Table B is because information in here can
be added to or deleted.

Right now I have 7 options in Table B. Well I want to
make all 7 option 1 cell in Table A.

Currently I have 7 cells for each option which I don't
want. Can I make it so all 7 options are in one Cell?
All the options are pull downs.

TIA!!