I'd check the memo fields to see if they contain any single quotes or other SQL control characters.

Good Luck,

There are certain differences when using large-size field types such as Memo (and I think this applies with MySQL's version of the Memo field as well, or so I've read) that can prevent them from being used in certain situations. I know I've run into this before and at the time it gave me some headaches, but it was some time ago. As I recall the solution was to use a regular text-type field instead. If you can deal with the 255 character limit, use a text field.

In principle, there shouldn't be any problem using memo-type data in mySQL. What field type are you using? If you are using only textual data, you have 4 text column types to choose from (TINYTEXT, TEXT, MEDIUMTEXT and LONGTEXT) with the latter able to story extremely large amounts of data. I frequently use MEDIUMTEXT to store fields which contain several pages of data such as HTML or RTF documents.

You may need to check that the data is being quoted correctly. If you are using DBI (and if you're not, you should be), you can use quote(). For example, the following utility subroutine will quote the text for you or replace it with "NULL" if empty (which you will need for an INSERT statement):

sub dbq{
my $x=shift;
if (length($x)>0) {$x=$db->quote($x);} else {$x = "null";}
return $x;
}

e.g.

$db = DBI->connect("dbi:mysql:$dbname$host$port",$user,$pwd);
$mytext=dbq($mytext);
$sql="insert into mytable (id, mytextfield) values ($myid, $mytext)";
. . . etc.

Try this sniplet (modify for your code)

open connection to STD database
$dbhSTD = DBI->connect('dbi:ODBC:test_database');
$dbhSTD->{'LongTruncOk'} = 0; #use 1 if it is ok to trunc data
$dbhSTD->{'LongReadLen'} = 512;

The LongReadLen value should be set to the size of your largest memo field length.