Jetforms syntax is
if(
@Address1. != ""), "print this", "else print this"
If someones address is
Chris Fraser
"Strawberry Fields"
Winding Road
Out West 9999
then the address is screwed up, the if statement gets printed on the letter. The same problem occurs when someones name is in the system as Michelangelo (Mick) Spaghetti. The brackets screw it up. One of Australia's largest super funds is manually rewriting letters because there is no workaround for this problem on the Jetforms side.
There are no problems with the data being in the database. No problems retrieving it, and yes all the non alpha numerics will have to be stripped out in the program code... which is CTL, a product of syncsoft. There are no problems at that end.
The shithouse BA I am working with wants to know how many members are affected by this problem. Currently data is very inconsistent. Eg some people are in system as O'BRIEN, some as O BRIEN, and some OBRIEN. Other than apostrophes, quotes, brackets and hyphens I doubt that there are any other issues. But they dont call em analysts for nothing.
selecting where field like (%''%) and like (%(%) will get me 99.9% of cases if not 100%. But what if there are other characters in there that could cause drama. I didnt want to have to write sql for every single different non alpha character. A select that would pick out any non alpha numeric would be schweet, but google is not my friend. I dont think one exists.