Determine Value of a field of currentrecord from another db

[acantho]

Is there any way to determine the contents of a field of the current record from a separate db?
Not looking for another way to solve the problem below since I'm just creating a simple example of what I'm thinking of.

example.

db1 fields
name
age
sex
response
lookup_calc

db2
response
age_restriction
sex_restriction
age_calc
sex_calc
lookup_calc

So in db2
age_calc = calculation based off the age of the entered in db1 in comparison to age_restriction in db2 returning something like a "yes" or "no"
sex_calc = calculation based off sex entered in db1 so if sex of current record in db1 = sex_restriction in db2 return something like "yes" or "no"


Then I could make a lookup where the lookup_calc match and I can bring over the matching responses from db2 to db1.

Any ideas?

 

[JeanW]

I can't see why you want the db2 data not in db1....

The information from db2 seems to be a logical outcome of choices in db1.

Restrictions are on recordlevel, no need to replicate these restrictions.

db2 should have the criteria for restrictions, where db1 makes a check and display the result, as boolean value f.i., in db1.

 

[acantho]

Thanks for the answer Jean.

The example was just for the purpose of showing what I was talking about.
And yes I realize in the example there are better ways of doing things... that's why it was just an example.

The actual project consist of several databases all pulling information based off answers returned from other databases, etc. etc.

I was just wondering if the above was possible as it would make my life a lot easier.
Right now, with my current knowledge, I'm seeing the need to create over 700 separate fields multiplied over several databases (it's big) in order to create the lookups needed.

In the end I'm trying to create value lists that are shorter then 100 items (right now they're in the 1000s) and lookups from different dbs.

If I could do the above I would be able to dramatically cut down the length of the lists and choices available in the end user db.

Am I making any sense or just rambling on?
LOL

 

[JeanW]

The only way to reduce such long valuelist is to use hierarchical valuelists or cascading valuelist, where you use the valuelist as key in a relationship to gradualy reduce the list with each step.

If you don't know how to do that, take a look at:

http://www.tek-tips.com/viewthread.cfm?qid=970318&page=11

HTH

 

[acantho]

Thanks again Jean.

I think I've possibly found a solution to my problem. First I had to determine that there is no automatic way to show Current Active Record

So I have to rely on a script which is alright Status(CurrentRecordID) and a global field allow me to determine the current record.

I can then make a relationship via a calc referencing that field and fields in other databases which can then be used by calculation to create yet another relationship which will finish off the final results to create the small value list.

And yes... it all starts with some hierarchical type list... though I am still interested in a drop down menu, but not for this project

If I run into any further snags I'll let you know

thanks again