I can see that the “bug” caused in SQL Server may be because the the Field Definition VARCHAR(MAX) may be not compatible with the SQLServer Version being used in XOJO (or something like that).
I noticed some praise given for ODBC Alternatives which I have tried, but get the following problem
VARCHAR(MAX) - Unknown (Used for large comment fields)
BIT - Unknown (Used for storing YES/NO Values)
Appreciate any comments on how you have all solved these hurdles
To change the way my original Tables were defined in MS Access 2000 (then imported to MSSQL Server 2012) would be a step backwards - but obviously very possible.