D
Dale
Hi there,
In brief, I have Word documents that are created in Word 2007 in a Vista
environment that have document variables in them that later need to be opened
up in both Vista/Word 2007 and XP/Word 2003 environments and encountering
problems with newline/CRLF's when opening up in XP/Word 2003.
So specifically, I have a VB6 application that populates some document
variables and I am encountering problems with how carriage return linefeeds
are interpreted. Word 2007 seems to be the issue in terms of compatibility
with Word 2003.
If the document is created in Word 2007 and saved as a .docx and I dump out
the varible and it's value, it looks like this:
strKids
this child 2009 Jun 01
that child 2009 Jun 05
the last two lines are separated by a new line which is good (and this is
how it always used to work when creating a .doc in Word 2003 and dumping out
the variables in Word 2003) but if I open this file in Word 2003 and dump out
the variables, I get this:
strKids this child 2009 Jun 01_x000d__x000a_that child 2009 Jun 05
Somehow the vbCrLf in a Word 2007 is messed up when it's interpreted by Word
2003. Any suggestions? Thanks.
In brief, I have Word documents that are created in Word 2007 in a Vista
environment that have document variables in them that later need to be opened
up in both Vista/Word 2007 and XP/Word 2003 environments and encountering
problems with newline/CRLF's when opening up in XP/Word 2003.
So specifically, I have a VB6 application that populates some document
variables and I am encountering problems with how carriage return linefeeds
are interpreted. Word 2007 seems to be the issue in terms of compatibility
with Word 2003.
If the document is created in Word 2007 and saved as a .docx and I dump out
the varible and it's value, it looks like this:
strKids
this child 2009 Jun 01
that child 2009 Jun 05
the last two lines are separated by a new line which is good (and this is
how it always used to work when creating a .doc in Word 2003 and dumping out
the variables in Word 2003) but if I open this file in Word 2003 and dump out
the variables, I get this:
strKids this child 2009 Jun 01_x000d__x000a_that child 2009 Jun 05
Somehow the vbCrLf in a Word 2007 is messed up when it's interpreted by Word
2003. Any suggestions? Thanks.