A bit more information. The discrepancy in the debugger the where 2 appears for a check mark only happens in v15 not v16.
I am fixing this in v16R6 in a data file that that has seen life through versions of 4D since version 3 days. It contains 3,702 records with the flag field set to the superscript 2 and 89,934 records contain a check mark. The v15 and v16 structures do not contain a check mark in the code only the superscript 2. Somewhere along the line I think the check mark got corrupted such that it was converted in the structure to the superscript 2. > On Aug 22, 2018, at 5:56 PM, JOHN BAUGHMAN via 4D_Tech <[email protected]> > wrote: > > For many years now I have been using a check mark, option-v on a Mac, to flag > a particular field. Today while working on a web site that was consuming that > field the site the field crashed the site when it contained the check mark. > When I traced it I discovered that the field in the debugger displayed with a > superscripted 2. > > If I search for records with the with the check mark using the following code > it finds those records correctly… > > QUERY([Appointment] ;[Appointment]In_chair="√”) > > When that same line of code is viewed in the debugger it looks like this... > > QUERY([Appointment];[Appointment]In_chair="²”) > > I am going to change √ to #, but I am wondering if anyone can explain this > strangeness? Is it a unicode thing? > > John > > > John Baughman > 1331 Auwaiku Street > Kailua, Hawaii 96734 > (808) 262-0328 > [email protected] > > ********************************************************************** > 4D Internet Users Group (4D iNUG) > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:[email protected] > ********************************************************************** ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
