Hi Aleksey:



>It looks like the same issue with empty character fields. Apparently Jet OLEDB provider fails when VFP tries to create zero length input parameter for ADODB.Command object. However, the same operation succeeds for SQL Server OLEDB provider. For example the code below works fine:

> ...

Ok, is f3 text the same as memo? There is no problem with a zero-length character field per se. It has to be memo.


You say that these are not a VFP problem. But why is it that

UPDATE sfproducts set proddescription=?sfproducts.proddescription where prodid=oldval(prodid,sf products)

fails if proddescription is memo and a zero-length string or > 255 in length, but these do not:

UPDATE sfproducts set proddescription="" where prodid=oldval(prodid,sf products)

UPDATE sfproducts set proddescription=repl("*",2000) where prodid=oldval(prodid,sf products)

?

Where does ?sfproducts.proddescription get converted to the actual contents of the field before updating OLEDB? It gets converted by VFP, right? It looks to me like VFP must not be doing the conversion correctly. Is there any way to look at the actual command sent to OLEDB? I tried AfterUpdate and the command is the same.

Anyway, I have my ap running now thanks to your help.

Are you with the VFP team at Microsoft? Do I need to call tech support to report this, or will you get it fixed?