Re: Word 2007 mailmerge
- From: Markus <Markus@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 23 Apr 2009 21:31:03 -0700
Peter,
Many thanks for all these details. I was hoping for this kind of info.
The app has been runing fine in Word 2003 for some time, so it does not go
back that far (relatively speaking). It is only installed on XP, so no Vista
issues yet.
One problem - I am using dbf files for the merge, and I get an OLE exception
error when the opendatasource executes. At first, I thought possibly the
install of Word 07 did not automatically install odbc for these files, but
odbc for dbf seems to be there.
Your item on the difficulty in using odbc drivers (especially Excel) sounds
like possible issue for my app. Have you seen anything on any special
technique for using odbc in 07 to open a datasource?
Many thanks again,
Mark
"Peter Jamieson" wrote:
The only comments I can really provide are in the area of connectivity.
and assuming your existing code works OK in Word 2003 there have been
few if any obvious changes to e.g. OpenDataSource, but numerous changes
in behaviour - some of these may be related to Vista rather than Office,
and some may even be Vista-64 "specials", but e.g.
a. it seems to be difficult to specify a DDE connection in code now
b. it seems to be difficult to specify an ODBC connection, certainly
to Excel
c. on Vista, the default folder for Data Sources is now some kind of
"search folder" that does not appear to pick up data sources recently
saved in the former default folder, i.e. the user's My Data Sources folder
d. Word will now tend to default to using the ACE provider rather than
the Jet provider it used previously, e.g. for Access, Excel, and some
delimited text file connections. (OTTOMH I couldn't point you to a
negative consequence of this, but the handling of ODBC may be one)
e. many "file type" data sources located on network drives appear to
be copied to local temp folders; if the user updates the data source in
Edit recipients, Word will typically fail when trying to save the data
source, prompting the user with the temp file name rather than the original.
f. as far as I can tell, Access/ACE has reverted to the idea that Jet
SQL is the norm and it does not appear to be possible or easy to switch
on SQL-92(?) as in previous versions - this has a potential impact on
the handling of queries with wildcard characters.
g. the XML in .odc now has a published schema and is different from
previous versions. However, Word still seems to maintain its
idiosyncratic interpretation of .odc
h. not sure .udl works any more in Vista
If your code hasn't been updated since (say) Word 2000 then there are
quite a lot more differences.
Peter Jamieson
http://tips.pjmsn.me.uk
Markus wrote:
I've had an app working for some time that allows users to create a template
word .doc file, picking fields from a table to merge from inside Word, then
using that template to generate multiple letters inside the app.
I am having problems getting this to work in Word 2007. There have been
multiple problems with the same code that has worked so well thru many
previous Word versions. I am not looking for specific advise on each problem
(yet), but general guidelines (if possible) for using mailmerge 07 over the
way it functioned in previous versions.
Can anyone outline some of the changes in mailmerge from previous versions
that I will need to consider in changing my code? Maybe someone has had to
update their app to use 07 for mailmerges and can give me some general
guidelines?
Thanks for any and all ideas on this,
Mark
- Follow-Ups:
- Re: Word 2007 mailmerge
- From: Peter Jamieson
- Re: Word 2007 mailmerge
- References:
- Word 2007 mailmerge
- From: Markus
- Re: Word 2007 mailmerge
- From: Peter Jamieson
- Word 2007 mailmerge
- Prev by Date: Re: Table clobbers style
- Next by Date: Re: Macro to add document path and filename to footer on first pag
- Previous by thread: Re: Word 2007 mailmerge
- Next by thread: Re: Word 2007 mailmerge
- Index(es):
Relevant Pages
|
