Connecting to external data sources is a new thing i'm learning so bear with me pls.
MYSQL is a natural choice for me over SQL Server as i have been using it a lot with php and i'm used to MYSQL workbench and phpmyadmin etc etc..
I loved the way that php had native support for mysql rather than use odbc, so i'd like the same functionality when connecting my Access front end to a mysql db. Therefor i want to use ADO with a .NET connector to MYSQL rather than linking tables with ODBC dsn which to me is cumbersone.
Today i been reading up on ADO in my Wiley Access 2013 Bible and i'm getting the gist of things.. Anyone familiar with using MYSQL on Windows probably knows its got Connector .NET v6.8.3 and an ODBC Connector which ships with the MYSQL for Windows installer..
I want to use VBA to create ADO objects to connect to the .net connector, I dont want to use ODBC. I got the ActiveX Data Object 6.1 library option enabled in Access which is the first stage, then my book said i should create a connection string file by creating blank text file with notepad and save it with a .udl extension then open it, to get the Data Link Properties dialog. I do this but when i click on the Provider tab, there is no OLEDB for MySQL option even though i'm sure i got it installed, so thats got me puzzled..
I know I'm kind of straying off the subject of Access, but there must be someone out there who has done this already and can help??
Does anyone have any experience of creating VBA code using ADO to talk to the MYSQL .NET connector? Is it possible? Or do i have to use ODBC?
I read that MYSQL .net connector is compatible with Visual Studio which i think implies that its compatible with VBA? Am i right? Am i wrong?
MYSQL is a natural choice for me over SQL Server as i have been using it a lot with php and i'm used to MYSQL workbench and phpmyadmin etc etc..
I loved the way that php had native support for mysql rather than use odbc, so i'd like the same functionality when connecting my Access front end to a mysql db. Therefor i want to use ADO with a .NET connector to MYSQL rather than linking tables with ODBC dsn which to me is cumbersone.
Today i been reading up on ADO in my Wiley Access 2013 Bible and i'm getting the gist of things.. Anyone familiar with using MYSQL on Windows probably knows its got Connector .NET v6.8.3 and an ODBC Connector which ships with the MYSQL for Windows installer..
I want to use VBA to create ADO objects to connect to the .net connector, I dont want to use ODBC. I got the ActiveX Data Object 6.1 library option enabled in Access which is the first stage, then my book said i should create a connection string file by creating blank text file with notepad and save it with a .udl extension then open it, to get the Data Link Properties dialog. I do this but when i click on the Provider tab, there is no OLEDB for MySQL option even though i'm sure i got it installed, so thats got me puzzled..
I know I'm kind of straying off the subject of Access, but there must be someone out there who has done this already and can help??
Does anyone have any experience of creating VBA code using ADO to talk to the MYSQL .NET connector? Is it possible? Or do i have to use ODBC?
I read that MYSQL .net connector is compatible with Visual Studio which i think implies that its compatible with VBA? Am i right? Am i wrong?