Bug #4272 'LOAD DATA LOCAL INFILE' Fails
Submitted: 24 Jun 2004 15:36 Modified: 1 Sep 2004 4:07
Reporter: Daniel Mayoras Email Updates:
Status: Can't repeat Impact on me:
None 
Category:Connector / ODBC Severity:S3 (Non-critical)
Version:MySQL ODBC 3.51 Driver OS:Microsoft Windows (Windows 2000)
Assigned to: CPU Architecture:Any

[24 Jun 2004 15:36] Daniel Mayoras
Description:
i recently upgraded from the 2.50.39.00 version of the MySQL ODBC driver to the 3.51.06.00 version and a process that had been working properly for over a year began to fail. 
the offending sql command is the 'LOAD DATA LOCAL INFILE' issued in MS Access VBA using DAO 3.6 via a .querydef using a .connection object. the exact statement is:
LOAD DATA LOCAL INFILE 'E:/RepairReports/Data/PUTmp.txt' INTO TABLE PARTmp_N 
FIELDS TERMINATED BY ',' 
OPTIONALLY ENCLOSED BY '"' LINES TERMINATED BY '\r\n' 
(SN,PART_CODE,DESIG,PART_INST,PART_COST,DATE,REF_NUM)

also, tables linked via ODBC into MSAccess 2000 with the newer 3.51 driver do not always display correct data, especially if i recreate the table contents with a 'TRUNCATE' followed by an 'INSERT INTO'. all fields and all rows show the word 'Deleted' instead of the correct data. the same tables, when connected with the older driver display properly.

How to repeat:
create a DAO connection using the ODBC DSN and create the .queryDEF object and then try the .Execute method and it will fail . . .
[1 Sep 2004 4:07] Miguel Solorzano
I tested with Access 2003, Connector/ODBC 3.51.09 and server
mysqld-nt.exe 4.0.20 without to repeat the behavior reported.

Please try with the latest release packages.