Hi Aleksey,

>I am glad you were able to find a workaround for the problem.
>Could you at least give a little bit more details about the problem? Are you using custom commands or default commands? Does it happen on Update, on Insert or on both? Does it report an error or corrupt data? Exactly what error is reported?

The issue is only on UPDATECMD when uploading a binary content >8K
(more specifically jpeg and tiff) into an IMAGE server type
(SQL server 2000 SP3a).

The IMAGE is mapped into a VFP NOCPTRANS MEMO field (thru the schema).
As i mentioned the issue disappears when changing the server type
to TEXT.

The content does not get corrupted but the action is not TABLEUPDATEd
at all.

>I understand that this is no longer your priority, but, please, try to find consistent repro.

I'm under high time-pressure this week. We appreciate that
MS is caring about the VFPtoSQL integration.

I'll come back as soon as i can. In the meantime, i copied the
result of the 1526 ODBC AERROR() code below. It may give you a hint on
what is happening in the cursoradapter<->ODBC communication.

The message is all the more curious... as it is created
when the "SQL server 2000" data type IS IMAGE and it stops
when changing the data type to IMAGE...

Kind regards

François

1-1526
2-Connectivity error: [Microsoft][ODBC SQL Server Driver]
[SQL Server]Operand type clash: text is incompatible with image
3-[Microsoft][ODBC SQL Server Driver][SQL Server]
Operand type clash: text is incompatible with image
4-"22005"
5-206
6-1
7-NULL