I don't see it in the documentation, but it seems whenever I try an append
command adding a value to a memo field, the query bombs. Here's a sample:
DoCmd.RunSQL "INSERT INTO Who (Type, Name, Note) VALUES('R', 'Test rec',
'nowhere')", False
Note is a memo field, you see; when I substituted another text field for it
the statement worked fine. Is it that way in every case? Is there a
workaround? Maybe I could add the record leaving any memo fields blank and
then fill them in afterward, somehow?
---
Bob Bridges, rhbridg@attglob al.net, cell 336 382-7313
(hotel) 612 869-7704 xt 118, fax 612 869-7383
/* A crooked politician may be faithful to his wife, but a man who deceives
his own wife can't be relied on to deal honestly with the public. We have
been getting this backward lately. We've been assuming that you can have
public virtue without private virtue. -Joseph Sobran, 1998 */
command adding a value to a memo field, the query bombs. Here's a sample:
DoCmd.RunSQL "INSERT INTO Who (Type, Name, Note) VALUES('R', 'Test rec',
'nowhere')", False
Note is a memo field, you see; when I substituted another text field for it
the statement worked fine. Is it that way in every case? Is there a
workaround? Maybe I could add the record leaving any memo fields blank and
then fill them in afterward, somehow?
---
Bob Bridges, rhbridg@attglob al.net, cell 336 382-7313
(hotel) 612 869-7704 xt 118, fax 612 869-7383
/* A crooked politician may be faithful to his wife, but a man who deceives
his own wife can't be relied on to deal honestly with the public. We have
been getting this backward lately. We've been assuming that you can have
public virtue without private virtue. -Joseph Sobran, 1998 */
Comment