Connecting Tech Pros Worldwide Forums | Help | Site Map

Word truncates Memo field when using Automation from Access

Laurie
Guest
 
Posts: n/a
#1: Nov 13 '05
I am using Automation in Access 2003 to open a Word Document and fill
in some values using bookmarks. It all works perfectly except for one
section.

I am filling in some values in a previously created Word Table, and the
memo fields are truncating to 255 characters. If I "manually" copy the
memo field into the Table, it has no problem accepting more than 255
characters.

Any suggestions on how to resolve this?

thank you!


jrchase@prodigy.net
Guest
 
Posts: n/a
#2: Nov 13 '05

re: Word truncates Memo field when using Automation from Access


Hum, this is just a guess, but it probably has to do with your query.
I have found that SELECT DISTINCT converts Memo fields to text fields,
hence truncating to 255 characters. Any time a Group By is used in a
query the Memo fields are converted to text fields.... I hope you find
your problem.

Laurie Almoslino
Guest
 
Posts: n/a
#3: Nov 13 '05

re: Word truncates Memo field when using Automation from Access


You are absolutely right - I was using "distinct" in the query, and
didn't know that causes Memo fields to truncate. This may also solve
some other long-standing mysteries!

Thank you very much!



*** Sent via Developersdex http://www.developersdex.com ***
David W. Fenton
Guest
 
Posts: n/a
#4: Nov 13 '05

re: Word truncates Memo field when using Automation from Access


Laurie Almoslino <laurie@pcdatabasesolutions.com> wrote in
news:928Ge.8$0B5.2212@news.uswest.net:
[color=blue]
> You are absolutely right - I was using "distinct" in the query,
> and didn't know that causes Memo fields to truncate. This may
> also solve some other long-standing mysteries![/color]

No, that has nothing to do with it.

I've encountered the same problem within Access, but triggered by
concatenating memo fields.

I think it's an inherent flaw in DAO and the inner workings of
Access.

The only workaround I found was to do the concatenation in the Word
file, which resulted in extra spaces, but that isn't a problem
because the destination is a web page, where HTML treats any white
space the same (one space is rendered as one space, two spaces are
rendered as one space, and so forth).

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
Closed Thread