are you using == "Labor"? Try ==Labor.
Consider the possibility that Filemaker is working correctly.
There are no such records.
Your data contains "Labor " or some variant.
It might be good to tell us more about this field. Does it contain other values, other text? Is is a checkbox field?
What happens if you enter find mode, then use command-I (insert from Index).
This should show you the list of actual values in the field.
If "Labor" is in fact one of those values, go ahead and insert that value.
(While still in find mode)
Then; before doing anything else; STILL in find mode; before performing the find, move the cursor around in the field, are there spaces before or after the "Labor" word?
1 of 1 people found this helpful
to add to my previous suggestion, you don't need double-quotes. More importantly, the space between the == and the criteria will break the find.
2 of 2 people found this helpful
To add detail to David's post, I created a sample file containing three records with the contents—labor, labor XXX, and labor YYY:
1. Each of the following Find criteria yielded the same result: labor, "labor", =labor, ="labor" (3 records found)
2. Each of these found only the first record: ==labor, =="labor"
3. Each of the following returned an error: = labor, = "labor", == "labor"
4. Spaces without = or == are ignored so do not cause the Find request to fail (I tested this with various combinations of leading and trailing spaces in fields)
1. quotation marks are not necessary in a Find request, but are ignored so do not cause the Find request to fail
2. a space after = or == breaks the Find
3. leading and trailing spaces are ignored, either in the Find request or in field contents, except when == is used.
It is worth spending some time trying various forms of Find request in order to better understand how the process works.
Thanks for the effort Keywords!
However I have tried various combinations of spaces and supplied the "labor" as a global variable eg.
$$variable, =$$variable and ==$$variable I will go back and try the suggestion again. I will also try Labor as a constant rather than from a global variable.
I´ll get back with my findings.
However I think its symptomatic to Filemakers documentation NOT to supply info like You now did, the user has to find out for him/herself instead, to much frustration. And if it wasn´t for the grand help of other users like You, we would use many good hours "experimenting" rather than making good progress with the applications.
Shame on FM´s documentation and thanks to You again!
And just how do You consider that might affect the question? "Why do I get different data sets with the same base material from labor, =labor and ==labor, with errors on the last two".
I don´t think You and I view things the same way Bruce, You often seem having difficulty to accept any critics against FM, so why don´t You just ignore my questions?
Maybe I should have been more specific? and said "detailed info on how to use commands in SCRIPTING"? The manual way, I am not considering in the applications I work with, other than as an option seldomly to be used.
But again, thanks alot for You energetic efforts!
Do you want help or don't you? Insert from Index is in fact a very useful way of discovering dodgy data. The index lists all unique values, so if a record contains, say, a leading space or a trailing carriage return it will show up as a separate entry from the same otherwise identical content, thus:
If you only look at an individual field's contents this sort of thing can be hard to spot.
This can be very helpful in cleaning up field content.
The problem I describe - not understanding your own data and the variations which you or users may have inadvertently put into the data - is a VERY common problem. I described basic skills and techniques you can use to observe your data.
Demonstrating your awareness of this facet of the problem makes it more likely that others will spend effort to help you.
+1 for Keywords' comments.
It was NOT an answer to You keywords, but to Bruce....
Exactly - but to make the description as short as possible, I choosed to show the problem with a constant rather than setting a variable and then using the variable.
And as I stated earlier the documentation on how to use all the commands (and the list of them are both long and strong) is thin, and requires to much experimentation for most users/developers. The learning curve is thus steeper than it should need to be.