I am a bit perplexed. I am dealing a lot with FM12 and its calculations and to be honest, a bug like this cannot be ignored.
But without suprise, no offense to you, i tested it and couldn't replicate it.
In addition, i noticed an error in your workaround : a semi-column is missing :Let ( [
fld = SourceHEREret = If ( fld = 1 ; 1 )
I am sorry Nigel but your bug is really a mistery for me. Could you please send me a screenshot of :1 ) Your Field List2 ) The field's formulaLet me know and have a nice day.Bye, FredPS : i am working on a Mac too, on 10.8.3 (and of course same last FMP version). I cannot imagine that is related with the 10.6 Mac OS.
Are you sure that you were using FileMaker 12?
This issue has been previously reported for Filemaker 11.
But like Fred, I can't reproduce this in Filemaker 12.03 on Windows xp. But then you are using a Mac system, so maybe the bug lives on in Mac systems.
For More Information see: Serious bug when renaming a field. Field name does not change inside Let function.
This is one of many acknowledged bugs that can be found in the Known Bug List thread here in the Report an Issue section of the forum.
It can also be downloaded as a database file from: https://www.dropbox.com/s/jt09b82i0xijbu3/FMP%20Bugs.zip
Thanks for your comments, and sorry about the missing semi-colon (now amended.)
The problem is reproducible for me with a brand new file, created using FM Pro 12 Advanced v12.03.
Here is a screenshot of the schema in its correct form:
and now with the Sorce field renamed:
yet when I try it, it get the results shown here:
Further tests reveal that if I include the , then I get the bug to appear.
All very, very specific in FileMaker 12
- You have to use the  --- a very common thing to use as you most often have to use them to get the calcaultion to work
- you have use If with an = operator.
Thank you for the posts.
I can also confirm this still occurs with FileMaker Pro 12.0v3.
Thank you for linking to the previous report.
Because of your diligence in linking these together, I was able to find the original report and add these new ones.
You may be justified in being proud, Phil, but FileMaker most definitiely are not!
By the way, the use of the square brackets is required if one is using multiple assignment statements: the main reason for using a Let Statement. There was only one assignment in my post, which was simply for illustrative purposes, but I retained the square brackets out of habit!
I am fully aware of when brackets are needed in let functions. It just happened to be the reason my test first failed to reproduce the issue. It did lead me to experiment with other expression variations just to see multiple levels of parenthesis had any effect but they don't change the results.