Hi everybody, I'm gonna ask a newbie question since I've used MySQL only
twice in my life, and it always was installed on a Linux box in my LAN (I
use WinXP). This time I wrote a routine which creates tables and inserts
data into them via ODBC (Driver version 3.51 both here and at the costumer's
site). Here it all works perfectly, but at my customer's site it's giving
errors; obviously, otherwise I wouldn't be here.
In my LAN environment I can insert records in a table, while at the customer
many errors are rised: the first was "Data too long for field xyz", where
the field xyz is a varchar(40) and I'm inserting exactly 40 bytes of data
into it. I cut it to 38 and now it stopped giving this error at the
customer's site, but now it throws an error on a datetime field: the datum
is empty so I just don't send any data to that field, and theyr MySQL
answers with "Incorrect datetime value: '' for column 'ORANAS_AN' at row 1".
The same operation, here on my local MySQL, works flawlessly for thousands
of records.

Note that the tables on the customer's MySQL DB have been created via ODBC
using the same routine (the same exact sequence of SQL commands) used to
create the tables in my LAN environment, so table structures are identical
and also the engine type and charset, since the "create table ...(" commands
all ended with the string
") ENGINE=InnoDB DEFAULT CHARSET=latin1"

This considered, there is obviously some difference between my MySQL and my
customer's one: or a version difference or a configuration difference or
both, as it seems.

Theyr errors begin with this string (they have MySQL on a Windows box):
[MySQL][ODBC 3.51 Driver][mysqld-5.0.37-community-nt]

My errors begin with this string (I have MySQL on a Linux box):
[MySQL][ODBC 3.51 Driver][mysqld-5.0.24a]

Is there any known difference in the ways these two versions/setups of MySQL
handle incoming data? Or are there differences in the default configuration
these two versions/setups use?

Where should I look to find those different settings which prevent my
commands to execute regularly on the customer's DB? I'm using both SQLyog
and direct ODBC access.

TIA anyone
--
Vilco
Think pink, drink rose'