And attached here is the modified library. I included all the "Master Copies" that I needed to get the whole production working.

SQLConfig DB still needs whatever connection/login settings entered that apply to your own specific case.

Not really a PLC guy but was tying to increase the SQL block size.

The "blank" space between characters I believe is for Unicode representation.  Unicode represents characters in a WORD (16 bits or WCHAR).  You said the CHAR version also inserts the blank space (should be NULL for Unicode), so maybe I am wrong.  

I would assume the PC side SQL would interpret the message as ASCII by removing the high byte and doing straight ASCII for the command.  If this is the case, why doesn't the WSTRING verison allow the full SSTRING limit instead of 1024 (512 real characters).  Worse case this would still almost double the messagesize from 254 characters.

The real goal is to have a large enough block size to basically eliminate the requirement for a stored procedure to concatinate multiple messages into on SQL call.