使用搜索功能查看 Kepware 的信息库,其中包含 500 多篇知识库文章。缩小搜索结果范围,或在下面的搜索字段中输入您的查询。

或者,如果您无法找到解决方案,我们还有另一个资源:我们的 PTC eSupport Portal。 如果系统提示您登录 eSupport Portal,您可以使用“我的 Kepware”凭据。需要一个“我的 Kepware”帐户吗?在此处创建

搜索解决方案结果:
View All Solutions

Kepware Knowledge Base: Solution


Using DataLogger, Advanced Simulator, and the ODBC Client Driver with MySQL 3.51 in a 64-Bit Environment


Last Update: 2018/11/7

Problem:

Users cannot connect on or from 64-bit operating systems.

Solution:
DataLogger, Advanced Simulator driver, and ODBC Client driver all use ODBC to interface with data sources that are ODBC-compliant. Connectors are used to access those data sources via a Data Source Name (DSN) created in the Microsoft Data Access Components (MDAC) interface. Those connectors are included for Microsoft data sources. For MySQL 3.51, a connector from the development organization is required and may be downloaded at Download Connector/ODBC. Users should make sure to download the x86 64-bit connector.

Connections are made via DSNs in the MDAC, which can be opened for one of the KEPServerEX ODBC-capable plug-ins or drivers (or for the operating system). Typing "ODBCAD32.exe" into the Run command line will launch the 64-bit MDAC, whereas the server will open the 32-bit MDAC. The 32-bit version is located in SysWOW64; however, because Microsoft wanted to give the same name to both the 32 and 64-bit versions (and the operating system always checks the System folder first for applications), users must provide the full path to the 32-bit version in order to launch it from the desktop. The full path should be C:Windows\syswow64\odbcad32.exe.

Because the server is a 32-bit application, it looks for 32-bit DSNs to use when connecting to ODBC data sources. For more information on the creation and use of 32 and 64-bit DSNs, refer to Unable to View a DSN Created by the ODBC Administrator.