If you leave them both OFF, you won't run into trouble. Use == for "exactly equals" and you don't need to mess with the setting command.
But set them both ON if that's what you want. With the two settings different, SEEK and SELECT yield different results. Think of ANSI as SET EXACT for SQL statements. On Fri, Apr 7, 2017 at 7:20 PM, <[email protected]> wrote: > Just ran across an instance where I had SET EXACT ON but didn't specify SET > ANSI (for which the default is OFF). After seeing a query for CHICAGO > contain results including others like CHICAGO HEIGHTS, I investigated and > thought my SET EXACT was OFF. Nope, it was ON but my SET ANSI was OFF. > Setting it to ON gave me the results I wanted. > > I'm just surprised this never bit me in all my years doing VFP; I guess > because I've usually been using a RDBMS (like MySQL/MariaDB). > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/cacw6n4sswbetokcxgqbaa0qh0yfye3uk+qscgdbbjybfivb...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
