You can see which one(s) are installed by starting ODBC Administrator (32bit) and looking at the drivers tab page. Some additional information on SQL Server clients:įollowing is a list of available SQL Server clients: NOTE: I did download and install both MS SQL ODBC 13.1 and MS SQL ODBC 17 from the MS site, but again their version numbers differ, and my problem persists Since I have been unable to find the download of that driver as a standalone installation, does anybody know of a quicker way to just extract and install the updated ODBC driver? Aside from being a real time-suck, I really don't want the studio to be on the users workstations. The only way I have been able to do that is to install the SQL Management Studio on each workstation. The problem is that all of my workstations need the version 14.2002.4 installed. However, if I install SQL Management Studio version 17.7 or higher, it installs the MS SQL ODBC driver 13 version 14.2002.4 (whish shows as version 2017.140.2002.4 in the ODBC Source Administrator). 5 (noted as 2015.1.5 in the ODBC Source Administrator). When I download the MS SQL ODBC driver 13 from the Microsoft site, it installs version. It simply seems that MS has not updated their download site to have the most up to date version of the version 13 ODBC driver. I think that really I just need to install the same ODBC driver that the Management Studio is currently using Lastly, once I get past this error (and 1 more similar error), I seem to be able to work fine, but nothing gets saved to the GLSESS file when I am working from the Workstation, but does when I am working from the server itself The mssqldrv.dll is identical on all computers. The server and the workstations all have ODBC 13 installed BUT the server version number says "201-169" whereas the workstations report "201-46" I even downloaded the ODBC driver 13 (and 13.1) from MS and they report a different number. Reading some of the forum posts, I see that the ODBC driver could be the cause. The Server and the workstations are all brand new Windows 10 computers. This happens on the two workstations but not on the server. HYC00 (0)-Optional feature not implemented Table = GLSESS (47) 22007 (241)-Conversion failed when converting date and/or time from character string. Then I uploaded them to my customers server and again everything opens fine, but ran into an issue when trying to open from a workstation.Ĭ:\Program Files (x86)\Grasp Software Corporation\Visual Grasp 4\Programs\vgprog.exe The files converted fine to SQL2017 and I had no issues opening and accessing them on my development computer. Today I converted a clients embedded data to SQL and ran into a wierd problem.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |