AnsweredAssumed Answered

Applescript find requests in calculation fields

Question asked by disabled_Ed-Case on Oct 31, 2010
Latest reply on Dec 3, 2010 by disabled_Ed-Case

Summary

Applescript find requests in calculation fields

Product

FileMaker Pro

Version

8, 9, 10, 11

Operating system version

Mac OS X 10.4, 10.5, 10.6

Description of the issue

I use applescript to query my databases and list results. The usual way of addressing them is by window and find request: e.g.

tell application "Filemaker Pro"
try
delete every request of window "MyDatabase"
end try
create request of window "MyDatabase" with data {"my search"}
find of window "MyDatabase"
end tell

This works fine on any indexed field apart from a calculation field - an error of "write access denied" results.
In my case such calculation field would be a concatanation of a number of other text fields - but sometimes their data has been in some way edited (for instance by limiting the max. number of words to say 10). Therefore I cannot simply write a number of queries for each find to accomodate these fields concatanated into my calculation field.
Simple question: what's the solution?

Steps to reproduce the problem

Try this applescript:

tell application "Filemaker Pro"
try
delete every request of window "MyDatabase"
end try
create request of window "MyDatabase" with data {"my search"}
find of window "My Database"
end tell

where the search is to be carried out on a calculation field (text, indexed)

Expected result

A find request that results in a number of (or no) records

Actual result

error message of "write access denied"

Exact text of any error message(s) that appear

Filemaker Pro got an error: Write access denied

Configuration information

My calculation field is made up of 3 text fields:
Field A: limited to a max. of 10 words
Field B: all words
Field C: all words

It should also be noted that the resulting error is precisely the same with no limit on any of the fields to be concatanated. i.e. this occurs with ANY calculation field

Workaround

There is none, as it is impractical on a database of 500,000+ records to create a new non-calculation field into which the desired concatanated fields can be written... the data changes often, it's time consuming and fundamentally it's unworkable etc.

Outcomes