Programmatic creation of ODBC DSN using SQLConfigDataSource

--_000_DE00E613E6C62C4BB8098F102FAFCC0C01B39786F136USMLVA0E925_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I am using the MySQL ODBC 5.2w Driver (5.2.3) and it appears that it does n=
ot follow the rules for SQLConfigDataSource. The specification for the SQLC=
onfigDataSource function says that the attributes should be separated using=
 a null byte and the list of attributes terminated with a 2 null byte seque=
nce, however the MySQL ODBC driver only uses the supplied attributes if the=
y are separated using semi-colons. This doesn't seem right.

Does anyone know when this was broken, or if there is any intention of fixi=
ng it?

Thanks for your input.


This message and any attachments are solely for the use of intended recipie=
nts. The information contained herein may include trade secrets, protected =
health or personal information, privileged or otherwise confidential inform=
ation. Unauthorized review, forwarding, printing, copying, distributing, or=
 using such information is strictly prohibited and may be unlawful. If you =
are not an intended recipient, you are hereby notified that you received th=
is email in error, and that any review, dissemination, distribution or copy=
ing of this email and any attachment is strictly prohibited. If you have re=
ceived this email in error, please contact the sender and delete the messag=
e and any attachment from your system. Thank you for your cooperation

--_000_DE00E613E6C62C4BB8098F102FAFCC0C01B39786F136USMLVA0E925_--