Looking deeper into ComCodeBook I find that the guts are using ODBC and Ado Record Sets to accomplish the task of communicating with the database. So the problem could stem from ODBC not being able to handle updating a large Memo field using an ADO Record Set. Have you heard of any problems with ODBC and large Memo fields? I have found a few things on the internet that indicate something of a work around for updating memo fields using 'AppendChunk' or 'UpdateChunk'. Any of this ring a bell with you?

TIA

>Bret,
>
>I'm not familiar wit ComCodeBook at all so you'll have to provide more info about the problem. Are you using ODBC or ADO to connect to data? Can you post the code from the frame work that does update?
>
>>I am using ComCodeBook to run several web applications. The web applications have been running with no problem for quite some time. But this week I had an engineer who contacted me about losing his remarks for a record he had in the database. The engineer's remarks are being stored in a memo field and the size of the memo field is about 13,000 characters. The data was entered into the memo field from another source outside the COM object. He can bring up the record via the web (using the COM object) and view the data no problem. But when he tries to update the remark data the ComObject loses the whole memo field. I have tried the sequence manually using VFP command window and I get the same results. ComCodeBook does not throw an error, but the memo field data is either gone or a few characters are saved. This is the code I ran via the command window:
>>
><snip>
>>
>>I know a lot of you are not familiar with ComCodeBook, but if you have any idea of why the memo field would not be saved I would like to hear it or if you have any past experiences in Record Sets and limitations I would like to know that also.
>>
>>TIA