Are the different "tags" in Photo_Tag separated by returns? That's what filtervalues expects and if the data is delimitted with other character such as commas or semi-colons, it won't work for you.
Your example expression using case is missing some quotation marks, but perhaps that's a typo.
Case (FilterValues( Photo_Tag; "Elevation")="Elevation"; Direction & "Elevation";
FilterValues( Photo_Tag; "Approach")="Approach"; Direction & "Approach";
Also, are you using a text field with an auto-entered calculation or a field of type calculation with text as the return type? (If using an auto-entered calculation, the field won't update when values in Photo_tag are modified unless you clear the "do not replace existing values" check box.)
The "tags" were entered into the field through the use of a checkbox set and are on different lines when looked at in table view so I assume that means they are separated by returns.
You are right that those were just typos in my post but were not in my actual calculation formula.
I am using a calculation field as c_photo_file_name where is the result is set to return as text. Photo_tag is a text field.
Again, thanks for any further insight.
Oh yes, I just remembered the annoying detail that is breaking your calculation. I generally avoid it with this syntax:
Case ( Not IsEmpty ( FilterValues( Photo_Tag; "Elevation") ) ; Direction & "Elevation" ;
Case ( FilterValues ( Photo_Tag; "Elevation") = "Elevation¶" ; Direction & "Elevation" ;
All the "values" functions append a return on the end of the result--which is very annoying to allow for in your calculations.
Your the man Phil. Thanks!