As another workaround, have you tried using the Filter Function? Listing every acceptible character in the string of filter characters might get pretty obnoxious, but it might in many cases eliminate the need for the custom function.
I can imagine doing that when dealing with ASCII, but not with Unicode....
BTW, what is the benefit of not needing a custom function (except for the case you want to use FileMaker Pro instead of FileMaker Pro Advanced for development)?
OK, there are other workarounds possible, such as pasting the null character into a global field and then using Substitute to replace every occurrence of null character in text with an empty string.
The point is that any workaround requires somehow modifying every text being pasted...
Not all people reading this thread may have FileMaker Advanced. Offering an alternative work around that does not require a custom function would be useful to them. I would also be interested in seeing the definition for the custom function that you are using.
For any of these methods, I'd use auto-enter calculations set directly on the text fields whenever possible. Your example of using a substitute function is one such expression that could work as an auto-enter calculation.
Please note that I'm not trying to suggest that this isn't a bug that needs to be fixed, just exploring workaround options that may be of use to those who encounter this issue.
You're right about the audience of this forum.
I am assuming (maybe incorrectly) that not many people who don't have Advanced will be really affected by this bug ;-)
BTW, I have included my custom function definition at the end my original post.