script won't work in filemaker Pro 10.

[GBSSHS]

Hello. I'm new at Filemaker Pro. So, please forgive me if I'm asking a simplistic question.

Here is what I wanted to do. I would like to enter data in a certain records's field, from "Table A".

Next, I would like to have a button setup that when it is selected, a script would be activated to search for records in "Table B." This search would look for records that have a certain field that matches the data that was entered in "Table A's" field.

I currently own a copy of Filemaker Pro 11. My computer is a Macbook using OS 10.

This is the script that I wrote.

• Set Variable [$$Enter Data: Table A::Temp Data]

• Perform find [Restore]

#NOTE: The specify Find request info in Perform Find [Restore] is: Find records Table B::Title: ["$$Enter Data"]

Here is my problem, this script works fine in Filemaker Pro 11. My client unfortunately, has an older version of Filemaker Pro 10. In that version, the script does not work. I suspect that Filemaker 10 does not support global variables but I'm not sure. Can anyone help me getting this script to work in the filemaker 10? Thanks. Graham

[bcooney]

Why can't the find be done directly in Table B?

Possibly, $var finds are not supported in FM10.

Also, it is more typical to use a global field to hold a value that would be used elsewhere. Perhaps more of an overview of what you need to accomplish would help us suggest the best approach.

[David Jondreau]

Table A and Table B are related aren't they?

Yeah, I think $var finds were introduced in 11. But it could be the quotes. The easy workaround is to:

Enter Find Mode[]

Set Field [ tableB::Title ; $$Enter Data ]

Perform Find[]

Also, I don't use spaces in variable names. I'm not sure if that just superstition, but I'd recommend not using spaces.

[bcooney]

Have you looked at the Go to Related Records script step? It allows you to "find" all records in a related table that "match" a field value.

[GBSSHS]

First of all, thanks for the quick response to my question.

Because of the suggestions and ideas I received from both of you, I started looking on how I had set up the relationships of the two tables. When I made the data input field "Global" it solved the problem. I would not have come up with this solution if it hadn't been for you guys. Thanks so much.

Graham