X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/998abc150616484b2bce17454cda2e1ff1f29b7b..43e995b6e39d41fd8a26f8bb9e6a6ef54bbcd324:/docs/latex/wx/tdb.tex

diff --git a/docs/latex/wx/tdb.tex b/docs/latex/wx/tdb.tex
index a1e9cef2a9..71a470d202 100644
--- a/docs/latex/wx/tdb.tex
+++ b/docs/latex/wx/tdb.tex
@@ -835,9 +835,9 @@ they also needed to take in to account different database manufacturers and
 different ODBC driver manufacturers. Because of all the possible combinations 
 of OS/database/drivers, it is impossible to say that these classes will work 
 perfectly with datasource ABC, ODBC driver XYZ, on platform LMN. You may run 
-in to some incompatibilities or unsupported features when moving your 
+into some incompatibilities or unsupported features when moving your 
 application from one environment to another. But that is what makes 
-cross-platform programming fun. It is also pinpoints one of the great 
+cross-platform programming fun. It also pinpoints one of the great 
 things about open source software. It can evolve!
 
 The most common difference between different database/ODBC driver 
@@ -918,6 +918,11 @@ As of v2.6 of wxWidgets, the wxODBC classes now fully support the compilation
 and use of the classes in a Unicode build of wxWidgets, assuming the compiler 
 and OS on which the program will be compiled/run is Unicode capable.
 
+The one major difference in writing code that can be compiled in either 
+unicode or non-unicode builds that is specific to the wxODBC classes is to 
+use the SQL\_C\_WXCHAR datatype for string columns rather than SQL\_C\_CHAR or 
+SQL\_C\_WCHAR.
+
 \subsection{wxODBC - Sample Code}\label{wxodbcsamplecode1}
 
 Simplest example of establishing/opening a connection to an ODBC datasource,