If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Best way to setup a field if different info needed based on type
Hello,
I'm stuck. I have a field that requires different info based on a type and I'm not sure how to setup that up. Basically, if field1 is equal to x, then enter this data (about 3 different fields) for field3. If field1=y, then enter a different set of data (two fields) for field3. I'm not sure of the best way to tackle this. Two different tables of the types (xtbl & ytbl w/relevant fields) linked by 1-M relationship to field3? Suggestions, please. Humbly, Cynteeuh |
#2
|
|||
|
|||
Best way to setup a field if different info needed based on type
You probably need some kind of cascading combo boxes. Could you describe your
date in more detail? -- Lynn Trapp "cynteeuh" wrote: Hello, I'm stuck. I have a field that requires different info based on a type and I'm not sure how to setup that up. Basically, if field1 is equal to x, then enter this data (about 3 different fields) for field3. If field1=y, then enter a different set of data (two fields) for field3. I'm not sure of the best way to tackle this. Two different tables of the types (xtbl & ytbl w/relevant fields) linked by 1-M relationship to field3? Suggestions, please. Humbly, Cynteeuh |
#3
|
|||
|
|||
Best way to setup a field if different info needed based on type
If you are saying that you want to copy data already in "3 different fields"
(or "two fields") into a new field, why? Why bother (redundantly) storing the same data? If you want to SEE the concatenation of "3 different fields" or "two fields", use a query instead of storing the calculated value (redundantly). (NOTE: this is not an absolute, but it is rare to actually need to store duplicate data like this ... as Lynn says, "more info, please!") Regards Jeff Boyce Microsoft Access MVP -- Disclaimer: This author may have received products and services mentioned in this post. Mention and/or description of a product or service herein does not constitute endorsement thereof. Any code or pseudocode included in this post is offered "as is", with no guarantee as to suitability. You can thank the FTC of the USA for making this disclaimer possible/necessary. "cynteeuh" wrote in message ... Hello, I'm stuck. I have a field that requires different info based on a type and I'm not sure how to setup that up. Basically, if field1 is equal to x, then enter this data (about 3 different fields) for field3. If field1=y, then enter a different set of data (two fields) for field3. I'm not sure of the best way to tackle this. Two different tables of the types (xtbl & ytbl w/relevant fields) linked by 1-M relationship to field3? Suggestions, please. Humbly, Cynteeuh |
#4
|
|||
|
|||
Best way to setup a field if different info needed based on type
Could you also clarify what you mean by a field being loaded with a "set of
data" and the particulars of what would go into it (e.g. some other fields?) |
Thread Tools | |
Display Modes | |
|
|