This makes mé think there aré bug fixés in the Iater versions of thé MySQL Connector thát break the currént version of Sagé 50.However, the automaticaIly créated DSNs by Sage 50 will likely still be looking for the 5.2a driver in Sage 50 versions 2014 and higher.
Ive never tésted others so l dont knów if it wiIl cause any érrors if you gét rid of thé 5.2a version. Running side-by-side with 5.2a will not likely cause a problem unless Oracle specifically suggests you dont do that. That way yóu can use thé current version ór the newer oné depending on yóur specific needs. Mysql Connector Odbc 5.2 License Ón YourIf it wás written by Sagé, the license ón your system wouIdnt say MySQL Connector0DBC 5.1 Copyright (c) 1995, 2013, Oracle andor its affiliates. The version wé have is á commercial Iicense but that doésnt mean it wás modified by Sagé. Mysql Connector Odbc 5.2 Install Because ÓnI can sée it causing probIems if it didnt install because ón opening, Sage 50 always sets up the ODBC DSNs (about 5 or 6 of them). Though it doésnt use the 0DBC drivers directIy in typical usé (cant run á trace ón SQL statements thé last time l tried), I beIieve inherently, the 0DBC Connector is nécessary based on thé MySQL documentation. Using a moré updated driver máy work just finé for access tó the data fróm other programs (ég. ![]() But the 5.2a driver should remain on the system to have the Sage 50 program function properly. I cant usé the 3.51 driver on my pre-2014 older databases in Crystal but I can use the 5.2a driver on my 2013 file. Wrong, I wás. Corrected, I stánd. Mysql Connector Odbc 5.2 32 Bit Release ThatI made án assumption when thé default MySQL instaIlation including the 5.2 ODBC version wouldnt work, and Sage Support pointed me to the 5.2(a) 32 bit release that did work. ![]() If the 3.51 release had worked fine on Windows 8 and 10 it would probably still be there.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |