Alright, lets see if I can explain this one. We create FileMaker databases about every 3 or 4 years or rework ones that previous co-workers have worked on.

Anyway

I have fields that I are calculated values with case statements. Case(Field1="1",1,Field1="2",2)

Instead of just assigning a static value I such as 1 I want to pull the value from Record 1 of Field1 in another Filemaker database. Can this be done and I assume I have to set up a relationships for that database / fields?

Not working on Filemaker everyday gets to you go to work on it. Thanks for any help?

Nathan

Hi Nathan, and welcome to the Forum,

Why not just have the calculation equal Field1,

i.e. in the Calculation Box,

Field1

BTW, the "" are not needed for numbers, only Text.

HTH

Lee

I was using as numbers to be short. It is actually text, but depending on what a user picks from the drop down list in another field (value-list) I want it to pull for selection 1 Field1:Record1 , selection 2 would be Field1:Record2 from this other database.

Thanks for the quick reply...

It would be easier if you explained what you're actually trying to accomplish by this. In general, if you have a related table of code/value pairs, it's easy to select a code on "this side" and fetch the corresponding value via the relationship.

It is a observation form. The observer has a drop down list from unsatisfactory, basic, proficient, etc... When that is chosen the text box on the next page (two page form) should auto fill the text the administration would like in that box. (predetermined in the other database) It will be used on a PDAs and then synced over to PC so that is can be modified after they are out of the classrooms.

Well then, if you call the terms unsatisfactory, basic, proficient, etc. "code" and the text the administration wants "value", then all you need is a relationship that matches the selected code with the code in the other table. You have a choice of either just displaying the matching value (by placing the related value field on the layout), or looking it up into a local field (so that it can be edited by the user). Either way, no calculation should be necessary.