>I have two identicles Dbf's, Sig1 and Sig2. with only one Memo field called sig_data. I am trying to store some biomatrix data created by a signature capture device.The data has bouch of 0, 1 and 2's in a continues string (about 19000 characters)
>
>Sig1.dbf - which is part of a dbc, was updated using ODBC drive via SQL passthrough commands.
>
>Sig2.dbf - is a standalone table which was updated without ODBC, by using foxpro REPLACE command.lcSig_data command.
>
>After update, I checked the length of the field len(allt(sig_data)) in both tables and it come up to the same number.
>
>However, the SIG2.DBF file had some extra zeros and the end and it reproduced the signature perfectaly. Meanwhile, the table I updated using ODBC had no zeroes at the end and failed to produce the signature.
>
>Can someone tell me why ODBC truncates characters in a memo field. Is there an alternate method to that. I tried to zip data data using zlib.dll but no luck.
>
>Thank you in advance...
>
>Raza Malik

Last ODBC driver for VFP was for VFP6 SP5.
You should use VFP OLEDB provider to work with VFP9 tables.