This is a known issue in the SQL Server driver. The workaround is to ensure that your text columns are the last columns in the table. Then the update works. I've heard that this is fixed in MDAC 2.5 but it's not out yet so I can't confirm that.
>Since others have shown a fascinating interest in ranting, and because it is so well supported on the UT, this is my turn.
>
>I have to work with ADO recordsets etc. on a web application. What I have just discovered, and what I find very annoying, is the fact that after I update a recordset with a field that maps to a sql server TEXT data type (a memo field) the data disappears from the field in the recordset.
>
>Have you ever heard of such nonsense? All the other fields seem okay but the field mapping to text data now has some wacky status (actualsize of data is -1). The recordset needs to be requeried in order to get the data back. Can you imagine what we, as VFP'ers would think if a memo field lost its data after a tableupdate?
>
>No doubt VB'ers and others have the stoicism and real world experience to deal with this kind of data outrage and perhaps I have been tainted by the elegance of VFP to have foolishly expected better characteristics from ADO.
>
>I say, what nonsense!
"It is an important and popular fact that things are not always what they seem. For instance, on the planet Earth, man had always assumed that he was more intelligent than dolphins because he had achieved so much -- the wheel, New York, wars and so on -- whilst all the dolphins had ever done was muck about in the water having a good time. But conversely, the dolphins had always believed that they were far more intelligent than man -- for precisely the same reasons." - Douglas Adams
