Connecting MySQL with Crystal Reports v10 - mysql

I am new to Crystal Reports v10 and I'm creating reports to embed in Visual Studio 2010 forms. The database server I'm using is MySQL. I have some issues regarding to creating new connection in crystal reports. Based on what I've read, I should select the ODBC in order for me to connect it to the MySQL. However, when I select ODBC and LocalServer and enter the username and password an error message occurred and shows Logon Failed. Am I doing it right? Is there anything you could help me please?
I already installed the MySQL Connector/ODBC 5.1

You need to install the MySQL ODBC Connector.. Create an ODBC data source from the Administrative Tools \ ODBC Data sources control panel. It will then be available in Crystal Reports.

You must download the appropriate version of mysql odbc connector since there are two of them:
mysql odbc connector Windows (x86, 32-bit), MSI Installer)
mysql odbc connector Windows (x86, 64-bit), MSI Installer)
if 64-bit doesn't run, try to uninstall it and try the 32 bit msi Installer
http://dev.mysql.com/downloads/connector/net/

Related

ODBC Driver 13 and ODBC Driver 11

Can I install both ODBC Driver 13 and ODBC Driver 11 on the same server?
I need to access Microsoft SQL 2008 database and Microsoft SQL 2016 database. First one requires ODBC Driver 11. Second one requires ODBC Driver 13.
Would they be independently use by the system?
Update:
I have installed both drivers 11 and 13. I still can't work with my 2008 database.
Not sure if I need to restart? Did not restart as installation did not ask for it.
It appears you can simultaneously install ODBC 11 and 13|13.1 since the filenames are different and even Microsoft suggests you can change the connection string. (I do not have yet a server with SQL 2016 on testing environment. Therefore, I can not test it).
How to differentiate which application will use which?
To quote from the Microsoft's pages:
When an application uses the driver, the application should indicate
that it depends on the driver through the install option APPGUID.
Doing so enables the driver installer to report dependent applications
before uninstalling. To specify a dependency on the driver, set the
APPGUID command-line parameter to your product code when silently
installing the driver. (A product code must be created when using
Microsoft Installer to bundle your application setup program.) For
example:
msiexec /i msodbcsql.msi APPGUID={ <Your dependent application's APPGUID> }

SQLCMD for windows 2003

I need to install SQLCMD utility on a windows 2003 Standard Edition SP 2 server. I tried to install download it from http://www.microsoft.com/en-in/download/details.aspx?id=36433. When I try to install, it asks for ODBC driver 11 for SQL Server. This driver is available at http://www.microsoft.com/en-in/download/details.aspx?id=36434. However this is not supported for Windows 2003 OS. I tried to look for the older version of SQLCMD utility that might use an older driver compatible with Windows 2003 server, but could not find it.
Can you pls. suggest any alternative or give any other suggestion?
Faced the same problem, solution that worked for me on my server 2003:
First installation of sqlncli.msi from https://www.microsoft.com/en-us/download/confirmation.aspx?id=16978 (you have to expand the Install instructions)
Then installation of SqlCmdLnUtils.msi (different from MsSqlCmdLnUtils.msi which failed) from the same page https://www.microsoft.com/en-us/download/confirmation.aspx?id=16978

Using the correct mySQL ODBC driver in windows

I am trying to connect MS Access with a local mySQL database.
To do this I downloaded the mySQL ODBC connector from the mySQL website and installed it. As I am on a 64-bit system I went for the 64-bit version.
I then discovered when trying to connect Access to mySQL that my installation of Office is actually 32-bit so the driver doesn't work. So I removed the 64-bit ODBC driver and installed the 32-bit one.
Problem is, when I go into control-panel -> Administrative Tools -> Data Sources (ODBC) and try to add a new data source, the only options for the mySQL drivers seem to point to the old directory where the 64-bit drivers were. It then fails as it can't find the dlls with system error 126.
How do I get it to show the 32-bit drivers?
Run the 32-bit manager by running this command:
c:\windows\syswow64\odbcad32.exe
Also you can use RegisterDatabase() function to create connection from your code.
I wrote wrapper function many years ago:
http://5codelines.net/kak-programmno-sozdat-odbc-dsn/.
Just skip russian language and use the code.
Prior to installing the ODBC MySQL driver 5.2.6 you need to install the Microsoft Visual C++ 2010 Redistributable Package for x64 or x86 or both (just search the Microsoft site for these and download from there). Other driver versions may require different versions of this MS VC++ Redist. Package, which can coexist side by side. By default server 2008 R2 comes with the 2008 version, so installing the 2010 is required. Before installing check in Programs and Features if not already installed. Depending on you application it may require the 32 bit or the 64 bit version. Without it you get the system error 126
Then install the drivers:
To install the 32 bit version run as administrator c:\windows\syswow64\odbcad32.exe which is the 32 bit version of "Data Sources (ODBC)"

Server 2008r2 x64 and ODBC Connector

server 2008r2 x64,
mysql 5.5.24 x86,
access 2007 x86
im trying to connect mysql backend to access 2007 frontend...
after I installed mysql-connector-odbc-5.1.12-win32.msi and rebooted server. that driver will not show up in the drivers tab of ODBC Datasource administrator.or in the list of drivers if i try to add a new driver
also installed mysql-connector-odbc-5.2.5-win32.msi also just to try newer version, that does not show up either. repaired both install, rebooted, reinstalled, same thing. all i see is a mysql driver...
any ideas whats going on?
UPDATE:
Used C:\Windows\system32\odbcad32.exe and same results.. no driver there...
really not sure whats going on... any special dependancies required? not sure what i could be missing.. as i said, neither driver is visible, yet both installed without error (to my knowledge, are there install logs???)
default path for both drivers during installation was c:\programs Files (x86)\MySQL\connector ODBC 5.1\ or c:\rograms Files (x86)\MySQL\connector ODBC 5.2\
any thoughts?
After installing 32-bit ODBC components onto a 64-bit machine you need to run the 32-bit ODBC Administrator, normally found at
C:\Windows\SysWOW64\odbcad32.exe
If you just go the normal Control Panel > Administrative Tools > Data Sources (ODBC) route then you will be looking at the 64-bit environment, and your 32-bit options will not be visible.

dsn for ms access 2003 in windows 7

I am trying to create a dsn for ms access in windows 7. But its showing:
"The setup routines for the Microsoft Access Driver(*.mdb) ODBC driver could not be found.Please reinstall the driver. " and
"Error found:
The specified DSN contains an architecture mismatch between the Driver and Application."
I am using Microsoft Office 2003 version. I have tried to run C:\Windows\SysWOW64\odbcad32.exe also. But still getting this error. Now can anyone please suggest me to solve this error..
Thanks
You can run the setup again for Office 2003 and make sure to install the appropriate ODBC drivers:
http://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/no-odbc-drivers-available-for-excel-or-access-in/001c234b-dfd5-4378-a325-c4f1482fb6fd
If you open ODBC, you should be able to the full list of drivers installed and verify that either the older ones from Office 2003, or the newer ones you installed, are available. If they are, you can create a new ODBC DSN or edit the existing one to point to the drivers you want.