Im using the code to perform a find in filemaker and getting a error message that the specified field is not found. Does anyone see what I'm missing
Enter Find Mode []
Set Field [Contact Data::-- ; "--" ]
Set Error Capture [on]
Perform Find[]
Im using the code to perform a find in filemaker and getting a error message that the specified field is not found. Does anyone see what I'm missing
Enter Find Mode []
Set Field [Contact Data::-- ; "--" ]
Set Error Capture [on]
Perform Find[]
And are you getting this error message when you perform the script or when you try to create the set field step?
The error your report sounds like you have entered an invalid expression into a calculation editor--which might be a problem entering the calculated result. You might even be in the repetition box in the set field step which would be an error here.
So showing us a screen shot of the actual script would help us to help you.
This is a x-post with stackoverflow:
Specifying a bogus name to a table and/or field is perfectly ok here.
I wonder if your context is correct. Are you ON a layout based on the table (TO), 'Contact Data'? or are you on a layout that has a TO that is related to 'Contact Data'? This is context. If you are not in the proper context when calling the script, then the field will not be found. The field need not be on the layout, but you need to be there (by script, preferably) when it's called.
Beverly
That doesn’t answer my question. The view option: table/list/form shouldn’t matter.
Enter layout mode.
In the status tool bar (if hidden, make it visible)
At top left, you’ll see a drop down with the name of the layout. To the right of it should be “Table:” followed by the name of the table occurrence selected for your current layout.
Let us know the exact text shown there.
I'd get your first version of the script to work first if you haven't already.
What data in your solution that is specific to a given user?
Do you have a table with the person's account name or some kind of ID that is generated during log in?
Or did you have something different in mind? (Such as a user's region, county, city....)
In your example the field name is literally --.
I doubt that is the real name of the field.