Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 661
  • Last Modified:

Table Definition - Set lookup values based on another field in table

I am working on an Access 2010 database (32 bit, accdb). Within this database I am attempting to create a dynamic data validation process, wherein the user can identify fields in tables they want validated, and define what they want those fields validated against.
I have two tables in this database listing the tables in the database that will be validated plus the table(s) that will be used for validation, and all of the fields in these selected tables (tblDdTable and tblDdField, respectively).
I am now creating a new table named tblDdRules. One of the fields in this new table is "TableName". This field is defined with a combobox lookup which queries the table names in tblDdTable. The next field is "FieldName". I would like to define a combobox lookup which queries tblDdField using the value in the prior field "TableName" as the key.
I know I can do this on a form. Is it possible to do this within the table definition itself?
0
shambalad
Asked:
shambalad
  • 6
  • 3
1 Solution
 
dqmqCommented:
This field is defined with a combobox lookup which queries the table names in tblDdTable.

Yes, Access supports that, but gives you grief in the long run.  Not recommended.  You can create a form for maintaining the table in a couple of clicks.

Also, you do not want both a fk reference to tblDdTable and tblDdField.   Only to tblDdField.



Is it possible to do this within the table definition itself?

I don't think so and that would not be a good idea, either.

You really don't want to
0
 
shambaladAuthor Commented:
OK - I hear you on the 'bad idea' bit, but humor me. You say it's possible.  
I am attaching a small database with the three tables mentioned in the first post.
Here is an image of the lookup defined for the TableName field. How would I set up the query for the FieldName lookup?
Image 1Lookup-Question.accdb
0
 
shambaladAuthor Commented:
OK - I didn't ask the right question. I don't really want to know whether this is a good or bad idea. I want to know how it's done. I'll open up a new question and rephrase.
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
dqmqCommented:
Must be some EE glitch, but I've responded twice with a detailed explanation that has found it's way to the bit bucket. Don't have time to write it up again.  FWIW, thanks for including the db, that helps a bunch for understanding your question.

Here's the shortened version.

I meant to say that technique is supported for the SourceTable column, but not for the SourceField column constrained by the SourceTable column as you want.

I've attached my design.   As per your request, I did not remove the column look ups, but improved them as best I could.

Finally, I also cleaned up the foreign key relationship issues that I suspected.  As a result, you may find it acceptable to maintain rules by drilling down from the tblDdTables or tblDdFields rather than lookups from tblRules.
Lookup-Question.accdb
0
 
shambaladAuthor Commented:
Thank you for getting back to me on this. I have attached an image of the dropdown for the FieldName combobox. Note how it is not being filtered for the value of the TableName field. This is what I was getting at. I would want to see only the fields for the tblElement table.
image 1
0
 
shambaladAuthor Commented:
After closing this question. I opened up a new one:
http://www.experts-exchange.com/Microsoft/Development/MS_Access/Q_27670885
I do try to avoid opening multiple questions on the same topic. Anyway, I closed out the other one.
I appreciate your help on this. I hear you all loud and clear on the merits of this approach, but at this point I simply want to know how this is done.
0
 
shambaladAuthor Commented:
FWIW:
Some years ago I was supporting multiple Access databases for a major Health insurer. The individual who originally created the databases had extensively used lookups in the table definitions, so I know just how much of a major PITA they can be.
I still want to know how I can create a lookup which filters based on the value of another field in the table.
0
 
dqmqCommented:
Within a table definition, there is no way to design a lookup rowsource that is "filtered" based on the value entered (but not yet updated) to another column of the same row.
0
 
shambaladAuthor Commented:
That's what I thought. In truth, that is what I was really trying to get at in my original question. Thank you for taking the time to follow up on this. I appreciate your help.
Regards,
Todd
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 6
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now