SQL/ODBC driver

[Gabriel2010]

Hello!

Not as verse in SQL as I'd like to, but keep learning
everyday.

When creating an SQL driver, two options appeared to be
checked by default, "Use ANSI quoted identifiers" and "Use
ANSI nulls, paddings, and Warnings check box". Should
they be left alone or should they be unchecked? ANy
consequences for unchecking both?

Also, "Perform translation for character data check box"
appears, same inquiry as above.

User connects remotely from another country to a Great
Plains application hosted by SQL2k.

Thanks in advance!

Glad to be here!

 

[ArtieChoke]

I've tried all the options and haven't noticed any problems - except in a 3rd party report writer program - which stores SQL query in the report. It generated the query by using ODBC, so if you first generated the query without quotes, then changed the DSN to use quotes - the report wouldn't run unless you regenerated the query.

Basically, if you leave the defaults as they are, you'll be fine.