Hi,

Does any one know if it is possible to store an entire lookup table in one cell?

This table will only be used to generate a list of problems once the item is selected.

For example:

Item | Problems
TV | No Immage;No Sound;No Remote;Missing
Cable | No Signal;Not Working;Missing
Vacuum | No Dust Filter;Cord Damage;Not Working;Missing

Currently all the data is stored in a table(15C by 268R). If this is possible I can store it in (2C by 70R).

If there isn’t any simple way to do this I know I can do it with a VBA. I was just wondering if there aren’t any special characters which can be used to achieve the same result.

Why in the world would you want to do this?

Why in the world would you want to do this?

I just want a simple way to store a user configurable dropdown list. The Lookup table is (15C by 268R) to store all the relevant info. I’m planning to use this on a PDA, which means my dbase will be very slow.

In the main form you select each of the following from a drop down list; item, location and problem. The list of possible item locations and possible item problems are unique to each item. All items, problems and locations are subject to change.

Currently I am repeating the item name and then listing each problem and then listing a location in separate columns after. This makes the table massive.

If I do this the Lookup table is (3C by 25). As my PDA is limited by its hardware and software, it seems the best way. I’m using sprintDB which reads access databases, apart from relationships and reports.

I am unsure of what the proper solution is in this case. Can you make any suggestions?

I don’t know if I am explaining my self properly, I have uploaded an excel spreadsheet showing the two sets of data. Perhaps that would give you a better idea. Drop down lists will be generated in the main form from this table.

The sheet labled initial is where i started with 15 colomns and repeating the item name. The sheet trial is where i combined the colomns and removed the item name repetition.

The main concern is the size and complexity of the database as i will be entering data on a PDA.

Any suggestions would be greatly appreciated.

If I understand you correctly, you have multiple dropdown lists to identify multiple attributes/problems for a single record, currently storing each attribute/problem in its own column for that record.
You want to find a way to store multiple attributes/problems in a single column.

If the above is a fair summary then:
- No, it's not easily possible
- It's probably a terrible idea anyway (storing multiple values in a single field nearly always causes problems when you want those values separated again)
- It suggests that your data is not normalized.

It sounds like you need a table of items, then another (child) table in which to store the attributes/problems of those items - with potentially multiple rows referring to one item, each row describing a different attribute/problem for that item

If I understand you correctly, you have multiple dropdown lists to identify multiple attributes/problems for a single record, currently storing each attribute/problem in its own column for that record.
You want to find a way to store multiple attributes/problems in a single column.

If the above is a fair summary then:
- No, it's not easily possible
- It's probably a terrible idea anyway (storing multiple values in a single field nearly always causes problems when you want those values separated again)
- It suggests that your data is not normalized.

It sounds like you need a table of items, then another (child) table in which to store the attributes/problems of those items - with potentially multiple rows referring to one item, each row describing a different attribute/problem for that item

Yes, I would normally do that how ever the PDA does not support relationships. So I am stuck!

Perhaps if I did it oldschool like MSDOS, but then im contradicting my self as in those days you would have such a complex lookup system...lol.
Bad humour aside, would you know of a way to do that with out using relationships?

But thanks anyways. Any other ideas?

Do you have the version of SprintDB that supports subforms?

Do you have the version of SprintDB that supports subforms?

Yes I believe it does.

According to their website, subforms are quasi-relational - it might be possible to enter the problems as rows in a subform.

Alternatively, maybe some other db program might do it - HanDbase, or ThinkDB...