Top post fixed - see below...)
in message news:<IU2Cc.169$ XXXX@XXXXX.COM >...
"Mal" < XXXX@XXXXX.COM > wrote in message
news: XXXX@XXXXX.COM ...
Hmmm...memo fields can sometimes be an issue, but I have not seen this
particular behaviour before.
What happens when you run the report directly from Access, instead of piping
it to Word? Does it go haywire there as well?
If you suspect the one record, try modifying your recordsource to be a query
which selects only that record and see if the problem persists. If so, you
may have a dicey record in the table. Usual practice with an data corruption
issue would be to perform a Repair on the database, but something in my
waters tells me there was a question over whether this was regarded as a
Good Thing (tm) for solving problems with memo fields. If you really do
narrow it down to a problem with that field, I would suggest you wait for a
more informative answer from one of the other experienced people in this
ng - I would hate to tell you to do something which only made things worse !
Would one of my esteemed peers in the group care to jump in here and shed
light on the pros and cons of attempting to solve problems with memo fields
by performing Repair?