At step 7, the global is not even created, not seen in the DataViewer's watch while $$ArrayBlaBla is. What's the problem? Do I have to separate out anything with & in the calculation?
The calculation contains no syntax error, otherwise you would have a global variable with the value "?" (no quotes). Therefore, the SQL statement returned nothing, meaning no record satisfied the query.
I should have seen that but the activities beforehand have been so flawless, easy to use. Looking at the code and tables, I had presumed a grave error or ignorance of Filemaker on my part yet the error lied in assuming users of the training package would use it the same year the package was created. But I still feel stupid. lol Should have looked at the data.
Great that you got it working. Welcome to fmsoup @backagain!
It happens to us all, having the thing right before our eyes and yet we don't recognise it. Two pairs of eyes see more than one pair of eyes... That second pair of eyes can be a fellow developer here @ fmsoup
Welcome to the soup @backagain . Be warned that there are some errors in the FileMaker Training series. It is an excellent resource but a couple of errors slipped past the editors. You may bump into something else that doesn't look right.
Yes, I found another bothersome error in the same activity. Posting soon.
Thanks for the warning.
Are there better beginner/intermediate training resources you know of? (so that I don't feel like deleting Filemaker off my drive while shouting every profane expletive I know)
I'd been going through Richard Carlton's Udemy courses but I was guided by a pro to this old FM 15 series as superior and complete.
The explanations are certainly good. This is the first example that doesn't work for me. Maybe someone like me just needs to make an accompanying errata sheet and post it on this site along with the course material.
I think it is an excellent resource. It is comprehensive and the examples are excellent. They have practical applications and they introduce fundamental concepts in a sensible way.
Yep. That was it.
Should have been written:
Create a new calculation field, or field of "type:" Calculation, with the option Calculation result is:Text.