sqlext | extend gorm and gocql | Object-Relational Mapping library

You need to use SQLGetData, passing SQL_C_WCHAR type, for example, if your column is text. Here's example how to get values of the single text column and put them to vector:

Okay, it seems I missed one of the checks I made somehow: odbcinst.ini is actually changed! During the 17.6 msodbc install, one line was removed. After adding it again, it started working immediately:

Why was this line removed, I don't know. Or, in case of fresh install, this line was never added to odbcinst.ini. Anyway, it works now.

This will not do what you think it does:

(SQLWCHAR*)"db1",

If SQLWCHAR* is a pointer to a wide-character, then casting a non-wide string-literal will not produce the results desired, since casting will not magically convert the non-wide string literal to a wide string. The ODBC function is failing due to the "db1" string ending up incorrect in some way when the function receives the string.

The proper way to deal with this is first, get the code to compile without any string-type to string-type casts. Casting string types is a sign that something may go wrong. Use the string type that the function requires.

This goes for any application -- if you're casting string types, you better know exactly what you're doing, as you may be circumventing C++'s type-safety by issuing a C-style cast to stifle the compiler error.

In this case, the string type is SQLWCHAR, thus creating a string (in this case, modifiable since the it isn't a const pointer) can be done:

SQLWCHAR name [] = L"db1";

and then the function will not need a cast on the second argument:

I have added the comments inside the code, which will help you to understand the code easily. Credits: Link

I finally found the solution, although this is for 12.2.0.1 and not 19

Many thanks to all,

Finally got the solution, as said by quentin used L wide string Literals

Below is the exact Connection string

switch (SQLDriverConnect(sqlconnectionhandle, NULL, L"DRIVER={SQL Server};Server=tcp:xyz.database.windows.net,1433;DATABASE=ProjectLIT;UID=auser;PWD=zzzzzz;Encrypt=yes;TrustServerCertificate=no;Connection Timeout=30;", SQL_NTS, retconstring, 1024, NULL, SQL_DRIVER_NOPROMPT))

This is a suggestion.

Try Visual C++ MFC Template.

Include belows.

The compiler can optimize code so that operations are omitted or ordered differently. The optimization is typically enabled in a Release build configuration.

The variable test in your code is a victim of such optimization because no code can read it back. You should ignore variable values if your code doesn't access it if optimization is turned on.

It is not true that binary data must be null-terminated (if that would be true, you could not insert any data containing a 0 value, like { 100, 0, 100, 0, 100 }).

1. You need to set correct values for the buffer length (size of the buffer).
2. You need to properly setup and initialize StrLen_or_IndPtr argument. For binary buffers, the value of StrLen_or_IndPtr must be the length of the data held in the buffer. Note that this must not be the same as the actual buffer size (but it must be <= buffersize). From the documentation of SQLBindParameter:

The StrLen_or_IndPtr argument points to a buffer that, when SQLExecute or SQLExecDirect is called, contains one of the following [..]:

• The length of the parameter value stored in *ParameterValuePtr. This is ignored except for character or binary C data.

See below a minimal example that compiles: