Gregory La Due

You could use a memo field, as the other post suggests, or a Long Binary field.
The second option takes a bit more code to pull off, since you need to use the
Get/AppendChunk methods, but is faster in most cases and is less space-hungry.

--
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Please post/reply to the newsgroup(s) so
that everyone can benefit from the discussion.

Regards,

Klaus H. Probst, MCP

       ICQ: 22454937
      The VB Box: http://members.xoom.com/kprobst/
~~~~~~~~~~~~~~~~~~~~~~~~~~~

When I do "recordset.Update" with any other field on the same database,
the update is properly propagated physically to the database.

However, when I do recordset.field("TheMemoField").Value
= "TestString",
the new field value is shown OK, but when I do
"recordset.Update", the new value is lost?
Even if I do recordset.update(vFieldName, vFieldValue), the new value
is not stored
on the database...

Should the new string value be null-terminated, or something?

ADO reports the field type as adLongVarChar(201) - Long String Value.

Using:
Microsoft Jet (Access 7.0 .Mdb)
Microsoft Visual Basic 5.0 Professional (Sp2)
ADO 2.1, through Microsoft Data Access Components 2.1(MDAC
2.1.1.3711.11)

Thank you for any help.

--
Daniel Pelletier

Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.

This is a bug in OLE DB Provider for Jet 3.51, there is a description
and, most important, a solution in Microsoft Support Article ID:
Q198532.

It works fine with Jet 4.00 OLE DB provider.

Thanks.
Dan

Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.