Problem with a 0.68 working with Access

Access 97
Mysql 4.1.12a-nt-max-log
MyOdbc 3.51.10.00

In test database

========================
# Host: 192.168.0.5
# Database: test
# Table: 'testnumber'
#
CREATE TABLE `testnumber` (
`ID` int(11) NOT NULL auto_increment,
`Import` double NOT NULL default '0',
PRIMARY KEY (`ID`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
========================

insert two rows with Import = 0.68 and Import=1

Create a new access database and link through MyODBC to testnumber table.

Open table with double click.

Modify Import = 1 to Import = 2 ---> OK
Modify Import = 0.68 to Import = 2 ---> I get an error "Write conflict.
Another user has modified data"

I'm spanish, so I actually see 0,68 on access table. And that's may be
the point, in fact, when access links to Ms Sql Server thru ODBC really
goes nuts about decimal point being comma (not just a case as I have
found now in mysql after several years of good experience). That's has
always being funny to me. Access works fine with mysql but take you to
hell when trying to work with MS Sql Server through ODBC.



--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc@m.gmane.org

RE: Problem with a 0.68 working with Access

Juan Pedro:

Para usar Ms Access con MySql necesitas una columna tipo timestamp en
cada una de las tablas que acceses desde Ms Access. Con Eso se va a
eliminar ese error que tienes. El error es de Access no de MySql pero
con lo que te digo que hagas se va a quitar el error.

Osvaldo Sommer

-----Original Message-----
From: Juan Pedro Reyes Molina [mailto:jreymol@terra.es]
Sent: Tuesday, July 05, 2005 9:19 AM
To: myodbc@lists.mysql.com
Subject: Problem with a 0.68 working with Access

Access 97
Mysql 4.1.12a-nt-max-log
MyOdbc 3.51.10.00

In test database

========================
# Host: 192.168.0.5
# Database: test
# Table: 'testnumber'
#
CREATE TABLE `testnumber` (
`ID` int(11) NOT NULL auto_increment,
`Import` double NOT NULL default '0',
PRIMARY KEY (`ID`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
========================

insert two rows with Import = 0.68 and Import=1

Create a new access database and link through MyODBC to testnumber
table.

Open table with double click.

Modify Import = 1 to Import = 2 ---> OK
Modify Import = 0.68 to Import = 2 ---> I get an error "Write conflict.
Another user has modified data"

I'm spanish, so I actually see 0,68 on access table. And that's may be
the point, in fact, when access links to Ms Sql Server thru ODBC really
goes nuts about decimal point being comma (not just a case as I have
found now in mysql after several years of good experience). That's has
always being funny to me. Access works fine with mysql but take you to
hell when trying to work with MS Sql Server through ODBC.



--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe:
http://lists.mysql.com/myodbc?unsub=osommerh@intelnett.com

--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.8.9/39 - Release Date: 7/4/2005


--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.8.9/39 - Release Date: 7/4/2005



--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc@m.gmane.org