Quantcast
Channel: MySQL Forums - Connector/ODBC
Viewing all 1136 articles
Browse latest View live

Random Runtime Error '3197' Assign text to DAO.Recordset ODBC MySQL VARCHAR() (1 reply)

$
0
0
I'm trying to assign text from a textbox to a dao.recordset record field that is attached to a MySQL VARCHAR() through ODBC. It's failing with an access conflict Runtime Error '3197'. At first i thought it was because i was converting a multiline textbox down to a single line replacing vbNewLine and vbCrLf with \n. I tried using a number of different replacement characters. At first i thought it was letting me pass in a straight string like "abc", but then it started failing to do that as well. i've tried all sorts of quotation gimmicks like """" & str_data & """" or "'" & str_data & "'". i started by passing variables directly, and then i broke it down. i'm really at a loss. there hasn't been a place in my 50000 lines of code that has had this problem. any suggestions would be appreciated. I'm still in dev phase, so no one else is using the program. naturally i did rebuild everything. it does write the information to the table. but it fails after it writes it. I have traced all instances of open recordsets. there aren't any. I can On Error Resume Next, but that sounds like a pretty weak solution.


Public Function Account_Notes(transaction_index As
Integer)
'************************************************************************************
'************************************************************************************
'************************************************************************************
'************************************************************************************
'************************************************************************************

Dim strSQL As String, str_slot As String,
ing, str_data As String

Dim str_client_id_code39 As String

Dim str_month As String, str_year As String,
ing, str_date As String

Dim rst_ctl As DAO.Recordset


'************************************************************************************
'************************************************************************************
'************************************************************************************
'************************************************************************************
'************************************************************************************

Dim input_account_notes(7) As String
input_account_notes(1) =
1) = "input_account_monthly_notes"
input_account_notes(2) =
2) = "input_account_ancilliary_notes"
input_account_notes(3) =
3) = "input_account_awards_notes"
input_account_notes(4) =
4) = "input_account_sale_notes"
input_account_notes(5) =
5) = "input_account_supplies_notes"
input_account_notes(6) =
6) = "input_account_other_notes"
input_account_notes(7) =
7) = "input_account_balance_forward_notes"


Dim fld_account_notes(7) As String
fld_account_notes(1) =
1) = "account_monthly_notes"
fld_account_notes(2) =
2) = "account_ancilliary_notes"
fld_account_notes(3) = "account_awards_notes"
fld_account_notes(4) = "account_sale_notes"
fld_account_notes(5) =
5) = "account_supplies_notes"
fld_account_notes(6) = "account_other_notes"
fld_account_notes(7) =
7) = "account_balance_forward_notes"


str_client_id_code39 =
39 =
Forms!frm_client!frm_client_information("input_client_id_code39")

strSQL = "SELECT *" & _
" FROM [Client Account]" & _
" WHERE [account_client_id_code39] = "
_code39] = " & "'" & str_client_id_code39 & "'" &
_
" ORDER BY [account_id] ASC"

Set rst_ctl = dbs_mac.OpenRecordset(strSQL,
SQL, Type:=dbOpenDynaset)

If rst_ctl.BOF Eqv True Then

[Procedures Core].EmergencyExitFunction
Function ("unable to load account record$.")

GoTo Line1

End If

rst_ctl.MoveLast


str_month = [Procedures
ures
Utility].MonthToNumericStr(Forms!frm_client!frm_client_account("input_account_month"))

str_year =
ar =
Forms!frm_client!frm_client_account("input_account_year")


str_date = str_year & "-" & str_month & "-01"

rst_ctl.FindFirst "[account_tracking] = " &
" & "'" & str_date & "'"

If rst_ctl.NoMatch Eqv True Then

[Procedures Core].EmergencyExitFunction
Function ("could not find date in account
tracking.")

GoTo Line1

End If


str_data =
ta =
Forms!frm_client!frm_client_account(input_account_notes(transaction_index))

str_slot =
ot = fld_account_notes(transaction_index)


rst_ctl.Edit
rst_ctl.Fields(str_slot) = """" & str_data &
ta & """"
rst_ctl.Update


Line1:

If Not (rst_ctl Is Nothing) Then

rst_ctl.Close

Set rst_ctl = Nothing

End If


End Function

ODBC 5.3.10-winx64 driver install error on Windows Server 2016 (no replies)

$
0
0
I can't install the MySQL connector 5.3.10 (64 or 32 bit) versions on my 2016 Windows Server.

Checking with the Windows Program Compatibility Troubleshooter I get told it is an incompatible program.

I also tried the win32 version (OS is 64 bit) and 5.2.7 64bit version all gives the same result.

Error message:

Error 1918. Error installing ODBC driver MySQL ODBC 5.3 ANSI Driver. ODBC error 13. The setup routines for the MySQL ODBC 5.3 ANS Driver ODBC driver could not be loaded due to system error code 126. The specified module could not be found...\myodbc5s.d...


The Windows Server is fully patched and largely untouched apart from having installed python 3 on it.

Is there a fix for this or do I need another OS?

SQLInstaller error 12: Invalid install path (no replies)

$
0
0
Hey,

So I'm trying to connect to an Access Database from Centos using unixODBC and I'm running into errors trying to install the MySQL driver on my system. Below is the system information:

CentOS version: centos-release-7-4.1708.el7.centos.x86_64
package: mysql-connector-odbc-5.3.10-linux-el7-x86-64bit

output of cat /etc/odbcinst.ini

# Example driver definitions

# Driver from the postgresql-odbc package
# Setup from the unixODBC package
[PostgreSQL]
Description = ODBC for PostgreSQL
Driver = /usr/lib/psqlodbcw.so
Setup = /usr/lib/libodbcpsqlS.so
Driver64 = /usr/lib64/psqlodbcw.so
Setup64 = /usr/lib64/libodbcpsqlS.so
FileUsage = 1


# Driver from the mysql-connector-odbc package
# Setup from the unixODBC package
[MySQL]
Description = ODBC for MySQL
Driver = MySQL
Setup = /usr/lib/libodbcmyS.so
Driver64 = /usr/lib64/libmyodbc5.so
Setup64 = /usr/lib64/libodbcmyS.so
FileUsage = 1

[ODBC]
Description = ODBC for Master
trace = yes
Driver = /opt/remi/php56/root/usr/lib64/php/modules/odbc.so
FileUsage = 1

[MySQL_ODBC5]
Driver = /usr/local/lib/libmyodbc5_r.so
Setup = /usr/local/lib/libmyodbc5S.so

output of myodbc-installer -a -d -n "MySQL ODBC 5.3 Driver" -t "Driver=/usr/local/lib/libmyodbc5w.so"

[ERROR] SQLInstaller error 12: Invalid install path

how do I go about resolving? Folllowed instructions to the t on site and this is what comes back :/

ODBC 32 Connection Fails, but works O.o? (no replies)

$
0
0
Greetings,

I have installed mysql community and have connected to it from a machine on the same network mysql workbench. When I setup the 32bit odbc connector and choose test the result is an error about not being about permission denied to that user@host with password yes. On the server I have set all users to match host % with grant all then flushed priv's.

Now even though the connector test is failing, I am still able to use the connector to contact the database on the server via ms access. I have exported several tables to mysql through the connector and the use of it is great.

Should I be concerned about this?

mysql vb6 remote connection (no replies)

$
0
0
i use mysql odbc 3.51 successfully in my pc, then i create a program in visual basic 6 connected with mysql. it is successful. then i use this program in my remote computer it shows error :'
run time error -2147467259 (80004005) [MySql][odbc 3.51 driver]Host 'circulation' is not allowed to connect to this Mysql Server.


so please help me

Can't Install ODBC 5.3.10 on Windows Server 2016 (no replies)

$
0
0
I'm getting Error message.

"Error 1918. Error installing ODBC driver MySQL ODBC 5.3 ANSI Driver. ODBC error 13. The setup routines for the MySQL ODBC 5.3 ANS Driver ODBC driver could not be loaded due to system error code 126. The specified module could not be found...\myodbc5s.d... "

I tried installing the latest C++ redistributable package. but it didn't work. I still get the same error message as Lasse Thomsen.

Some other google advice said to find MSVCR120.dll and put it into the System32 folder. I found it in the Java Package and copied it to System32

This let the ODBC Installer complete successfully but when I tried to test the DSN connection I received an Error 126 module could not be found C:\Program Files\MySQL\Connector ODBC 5.3\myodbc5w.dll.

I followed the path in the error message and that file is actually there.

Any suggestions?

How to connect to MySql from Excel 2016 for Mac (no replies)

$
0
0
Hi,

I have been using Excel 2011 for Mac for a couple of years to connect to a MySQL database using the ODBC Connector. This morning I upgraded to Excel 2016 for Mac. Unfortunately this has broken my connection to MySQL. I can't access MySQL now from either Excel 2016 or 2011. Error message is "IM003: [iODBC][Driver Manager] Specified driver could not be loaded"

I've reinstalled the ODBC Connector to make sure it is the latest version.

Has anyone out there been able to connect Excel 2016 for Mac to MySQL?

Thanks,
Anthony

Access loses its connection/authentication to the MySQL database (randomly requests username password) (no replies)

$
0
0
I have an Access 2002 Database running on Microsoft Server 2003 with MySQL OBDC connector version 5.1 linking to an offsite MySQL database.

For a couple of years, it ran perfectly. I could close and open the Access application and it would always have access to the tables in the MySQL database. Never a problem or a glitch. Never asked for the username or password since the day I created the connection to the MySQL database.

One day in the middle of its nightly operations it displays the login screen asking for the MySQL username and password to be filled in. (suspending its operation) In the morning I would type it in, and it would continue on. From that day on, it randomly pops the MySQL username and password connect screen as well as every time I restart the Access application.

Nothing that I know of on my end changed so I assume it was something on the other end. A new version of MySQL server or a setting change? Does anyone have and idea as to what might have changed?

This is driving me crazy as it is randomly preventing some mission-critical maintenance from happening overnight.

MySQL 8.0: Connector/ODBC (no replies)

Classic ASP with ODBC 8.0.11 not possible? (2 replies)

$
0
0
Hello

I read there will be no more 32-bit version of the driver. How can I use my Classic ASP pages with ODBC now? ;-((( They require 32-bit driver.

Is there a tehnical reason why you discontinued this?

I can use 64-bit mysql but I can not use 64-bit myODBC.

Will mysql 8.0 continue to work with ODBC 5.3 (will 5.3 be further developed)? I mean, except the new features of the ODBC driver with SSL...?

Thank you

Jerry

SSIS MySQL destination ODBC 5.3 (1 reply)

$
0
0
Have an SSIS data flow task with MS Access data source and MySQL ADO destination. All columns in MySQL destination table are nullable with date, time, double, small int, char, varchar and text data types.

When the data flow runs, about 5% of the rows fail to load, seemingly related to the date or time columns, but the vast majority succeed with the exact same date or time values. It seems to be that when certain records are processed together, one always fails. But when each row is loaded individually through a foreach loop, they all load successfully. Can anyone tell me why MySQL won't successfully process the rows when presented in bulk? And more importantly, how do I fix it?

I have tried this using the MySQL ODBC 5.3 provider and the MySQL Net Connector 6.9.6 with the same result. Is there a parameter in either of these providers I need to set or change?

Any assistance would be greatly appreciated.

Parse UID and Password from access form (no replies)

$
0
0
Hi All

I have just upgraded the data back end of an Access project to MySQL using ODBC to link the tables.

I want to know if there is a way to send the UID and Password of the MySQL database from access to prevent the MySQL ODBC Connector Screen from popping up for authentication. I have my own User security setup in the front end so I just want access to all the linked tables when they enter their personal user and password information at the front end login. I prefer not to write ADO connection strings for every form data source or query.

I hope I have explained this properly

Kind Regards
Brice

What version mysql odbc driver? (no replies)

$
0
0
I have an Access 2010 db using mysql BE, distributed to several users, in whch the connection is dnsless. I have been instructing users to install mysql-connector-odbc-5.1.8-win32 (that was current version when this was developed). Now I am forced to move to Access 2016 (MS broke some features in 2010 and I am tired trying to get a fix). I will begin recommending AccessRuntime 2016 for those without Office installed but don't know which connector is best to specify. Help would be appreciated--want to keep everything in synch! Also, if they already have the 5.1.8 version installed, do they need to uninstall it?

8.0.11 ODBC Connector with MS Access 32 bit version dead? (no replies)

$
0
0
So no 32Bit install for the 8.0.11 ODBC connector - another thread mentioned Classic ASP connectivity going down the drain - this also kills 32bit Access applications - no upgrade to MySql 8 for us then!

ODBC Connector 5.1 randomly won't connect anymore. (no replies)

$
0
0
I've been using the same connection for ages and so have many others in my company but all of a sudden this morning it won't connect but comes up with error

Connection Failed: [HY000] [MySQL][ODBC 5.1 Driver] Can't create TCP/IP socket (10022)

All the other machines are working fine, I've tried re-installing the driver and it connects fine when you test the connection in the ODBC Data Sources configuration gui.

The Connector pops up with all the correct information loaded into the relevant fields but doesn't seem to be able to retrieve a list of databases.

I've tried checking my antivirus, I can't find anything in the logs and I've tried turning it off but it doesn't make any difference.

Any ideas?

Error connecting to MySQL 8.0 with ODBC 5.3 (Excel) (no replies)

$
0
0
Hi.

After upgrading MySQL to 8.0 on Windows 64bit, I cannot connect through ODBC MySQL Unicode Driver 5.3.10 (32bit) from Excel 2016 (32 bit).

I get this error:
[MySQL][ODBC 5.3(w) Driver][mysqld 8.0.11]Source character set not supported yb client.

The connection string I'm constructing is:
Driver={MySQL ODBC 5.3 Unicode Driver};Server=localhost;Port=3306;Database=dbname;Uid=myusername;Pwd=mypwd;OPTION=16427;

The connection is opened OK, but the error is trapped when accessing the DB for recordset.

(The DB is OK, as I can access it from the Workbench and from another Python application and apply SQL statements).

Please help :)

MySQL ODBC 8.0.11 Crash (no replies)

$
0
0
I am attempting to use the ODBC driver to create a linked server in SQL Server 2008 R2. I am able to get the linked server set up without any problems and am able to query, but when I start to run a large number of queries through the ODBC driver crashes and crashes SQL Server as well.

I set SQL to run the ODBC driver out of process, which at least allows SQL server to stay up, but the driver itself still crashes.

Below is a crash dump from running ODBC out of process.

Version=1
EventType=APPCRASH
EventTime=131709596121836000
ReportType=2
Consent=1
ReportIdentifier=47ff7161-5921-11e8-8d2f-065eed35e64c
IntegratorReportIdentifier=47ff7160-5921-11e8-8d2f-065eed35e64c
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=DllHost.exe
Sig[1].Name=Application Version
Sig[1].Value=6.1.7600.16385
Sig[2].Name=Application Timestamp
Sig[2].Value=4a5bca54
Sig[3].Name=Fault Module Name
Sig[3].Value=ntdll.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=6.1.7601.23455
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=573a54b7
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=000000000004eef1
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.16.7
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=066e
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=066ebec570da383f419878092f71f66d
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=343f
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=343f90a8d1683520f290caeead9c5bd1
UI[2]=C:\Windows\system32\DllHost.exe
UI[5]=Check online for a solution (recommended)
UI[6]=Check for a solution later (recommended)
UI[7]=Close
UI[8]=COM Surrogate stopped working and was closed
UI[9]=A problem caused the application to stop working correctly. Windows will notify you if a solution is available.
UI[10]=&Close
LoadedModule[0]=C:\Windows\system32\DllHost.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\system32\kernel32.dll
LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll
LoadedModule[4]=C:\Windows\system32\msvcrt.dll
LoadedModule[5]=C:\Windows\system32\ole32.dll
LoadedModule[6]=C:\Windows\system32\GDI32.dll
LoadedModule[7]=C:\Windows\system32\USER32.dll
LoadedModule[8]=C:\Windows\system32\LPK.dll
LoadedModule[9]=C:\Windows\system32\USP10.dll
LoadedModule[10]=C:\Windows\system32\RPCRT4.dll
LoadedModule[11]=C:\Windows\system32\IMM32.DLL
LoadedModule[12]=C:\Windows\system32\MSCTF.dll
LoadedModule[13]=C:\Windows\system32\CRYPTBASE.dll
LoadedModule[14]=C:\Windows\system32\CLBCatQ.DLL
LoadedModule[15]=C:\Windows\system32\ADVAPI32.dll
LoadedModule[16]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[17]=C:\Windows\system32\OLEAUT32.dll
LoadedModule[18]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[19]=C:\Windows\system32\rsaenh.dll
LoadedModule[20]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[21]=C:\Program Files\Common Files\System\Ole DB\oledb32.dll
LoadedModule[22]=C:\Windows\system32\MSDART.DLL
LoadedModule[23]=C:\Windows\system32\bcrypt.dll
LoadedModule[24]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.18837_none_fa3b1e3d17594757\Comctl32.dll
LoadedModule[25]=C:\Windows\system32\SHLWAPI.dll
LoadedModule[26]=C:\Program Files\Common Files\System\Ole DB\OLEDB32R.DLL
LoadedModule[27]=C:\Windows\system32\comsvcs.dll
LoadedModule[28]=C:\Program Files\Common Files\System\Ole DB\msdaps.dll
LoadedModule[29]=C:\Program Files\Common Files\System\Ole DB\msdasql.dll
LoadedModule[30]=C:\Program Files\Common Files\System\Ole DB\MSDATL3.dll
LoadedModule[31]=C:\Windows\system32\ODBC32.dll
LoadedModule[32]=C:\Windows\system32\odbcint.dll
LoadedModule[33]=C:\Program Files\Common Files\System\Ole DB\MSDASQLR.DLL
LoadedModule[34]=C:\Windows\system32\CRYPT32.dll
LoadedModule[35]=C:\Windows\system32\MSASN1.dll
LoadedModule[36]=C:\Windows\system32\bcryptprimitives.dll
LoadedModule[37]=C:\Program Files\MySQL\Connector ODBC 8.0\myodbc8w.dll
LoadedModule[38]=C:\Program Files\MySQL\Connector ODBC 8.0\LIBEAY32.dll
LoadedModule[39]=C:\Windows\system32\WS2_32.dll
LoadedModule[40]=C:\Windows\system32\NSI.dll
LoadedModule[41]=C:\Windows\system32\VCRUNTIME140.dll
LoadedModule[42]=C:\Windows\system32\api-ms-win-crt-runtime-l1-1-0.dll
LoadedModule[43]=C:\Windows\system32\ucrtbase.DLL
LoadedModule[44]=C:\Windows\system32\api-ms-win-core-timezone-l1-1-0.dll
LoadedModule[45]=C:\Windows\system32\api-ms-win-core-file-l2-1-0.dll
LoadedModule[46]=C:\Windows\system32\api-ms-win-core-localization-l1-2-0.dll
LoadedModule[47]=C:\Windows\system32\api-ms-win-core-synch-l1-2-0.dll
LoadedModule[48]=C:\Windows\system32\api-ms-win-core-processthreads-l1-1-1.dll
LoadedModule[49]=C:\Windows\system32\api-ms-win-core-file-l1-2-0.dll
LoadedModule[50]=C:\Windows\system32\api-ms-win-crt-string-l1-1-0.dll
LoadedModule[51]=C:\Windows\system32\api-ms-win-crt-heap-l1-1-0.dll
LoadedModule[52]=C:\Windows\system32\api-ms-win-crt-stdio-l1-1-0.dll
LoadedModule[53]=C:\Windows\system32\api-ms-win-crt-convert-l1-1-0.dll
LoadedModule[54]=C:\Windows\system32\api-ms-win-crt-time-l1-1-0.dll
LoadedModule[55]=C:\Windows\system32\api-ms-win-crt-utility-l1-1-0.dll
LoadedModule[56]=C:\Windows\system32\api-ms-win-crt-math-l1-1-0.dll
LoadedModule[57]=C:\Windows\system32\api-ms-win-crt-environment-l1-1-0.dll
LoadedModule[58]=C:\Windows\system32\api-ms-win-crt-filesystem-l1-1-0.dll
LoadedModule[59]=C:\Windows\system32\api-ms-win-crt-conio-l1-1-0.dll
LoadedModule[60]=C:\Program Files\MySQL\Connector ODBC 8.0\SSLEAY32.dll
LoadedModule[61]=C:\Windows\system32\Secur32.dll
LoadedModule[62]=C:\Windows\system32\SSPICLI.DLL
LoadedModule[63]=C:\Windows\system32\MSVCP140.dll
LoadedModule[64]=C:\Windows\system32\api-ms-win-crt-locale-l1-1-0.dll
LoadedModule[65]=C:\Windows\system32\api-ms-win-crt-multibyte-l1-1-0.dll
LoadedModule[66]=C:\Windows\system32\odbccp32.dll
LoadedModule[67]=C:\Windows\system32\VERSION.dll
LoadedModule[68]=C:\Windows\system32\mswsock.dll
LoadedModule[69]=C:\Windows\System32\wshtcpip.dll
LoadedModule[70]=C:\Windows\System32\wship6.dll
LoadedModule[71]=C:\Windows\system32\DNSAPI.dll
LoadedModule[72]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[73]=C:\Windows\system32\WINNSI.DLL
LoadedModule[74]=C:\Windows\system32\rasadhlp.dll
LoadedModule[75]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[76]=C:\Windows\system32\NLAapi.dll
LoadedModule[77]=C:\Windows\system32\napinsp.dll
LoadedModule[78]=C:\Windows\System32\winrnr.dll
LoadedModule[79]=C:\Windows\system32\ntmarta.dll
LoadedModule[80]=C:\Windows\system32\WLDAP32.dll
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=COM Surrogate
AppPath=C:\Windows\system32\DllHost.exe

MS Access ODBC Copy Table to Access Drops Primary Keys (no replies)

$
0
0
We are using Access as a front-end to MySQL. Everything works fine when we use live ODBC Links to the MySQL tables that are on a server. We are using the MySQL 5.2 driver.

For development, we sometimes use the ODBC "Copy" tables to get the actual tables in our local machine. In this case, none of the tables have primary keys. This causes several problems with queries.

However, if we use the "Convert to Local Table" function, the resulting local tables do have the correct primary keys.

All of the users are on Windows 10 and use Access 2007,2010 and 2016. We have the same problem with all of the machines.

Thanks in advance for any help with this issue.

Source character set not supported by client error on SHOW TABLES command (no replies)

$
0
0
I'm connecting to MySQL Server 8.0.11 using Excel VBA using ODBC 5.3 driver.
I can execute most statements and queries without a problem (including DDL statements and LOAD FILE LOCAL).

One statement, SHOW TABLES FROM <schema> LIKE '<table_name>' is causing an error:

Microsoft Visual Basic

Run-time error '-2147467259 (80004005)':

[MySQL][ODBC 5.3(w) Driver][mysqld-8.0.11]Source character set not supported by client

This is persistent with ODBC 5.3.4 through 5.3.11 driver (32 bit).

This (equivalent) statement also produces this error:

SELECT * FROM information_schema.tables WHERE table_schema = 'xxxx' AND table_name = 'xxxx' LIMIT 1;

my.ini has:
[mysqld]
character-set-server=utf8
collation-server=utf8_general_ci

The schema and table columns are all created with utf8 correctly.
Running on Windows10 64bit hosting both Excel (Office 2016) and MySQL.

Connection string (ADODB):

Driver={MySQL ODBC 5.3 Unicode Driver};Server=localhost;Port=3306;Database=xxx;Uid=xxx;Pwd=xxx;charset=UTF8;OPTION=16427;

connection user has privileges on all schemas, no limitations, with all global privileges granted, except: CREATE TABLESPACE, CREATE USER, RELOAD, REPLICATION CLIENT, REPLICATION SLAVE, SHUTDOWN, SUPER

Odbc error with Win 10 Update (no replies)

$
0
0
I have an application made with Visual Basic 6.0 and using ODBC Connector 5.3.4 32 bits. Until today everything worked fine, but today in the computers that I have installed Windows 10 has stopped working as a result of the last update April 2018. If in these computers I remove the last update of windows, everything returns to work correctly. When the application does not work it tells me that it can not find the address of MySql, but if I attack by the browser with PhpMyAdmin it finds it.

Could someone help me?

Translated with Google Translator
Viewing all 1136 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>