Matt,
I use many of the .odc connections, but all going to excel. Trying this
in MS WORD with the ODC, did give me the "too few fields" as you
described.
So my question is, could you allow the connection in Excel, and then point
your mail merge to the spreadsheet.
Instead of going from odc to word, you would be essentially going odc to
excel, then mail merge word to the excel doc.
That did work for me.
Diane Mueller
From: Matt Olson <Matt.Olson@xxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 12/04/2017 01:59 PM
Subject: Anyone able to successfully get .odc (Office Data
Connection) files to work with DB2?
We have historically created mail merges using the ancient MS Query option
in Word. MS Query no longer functions properly under the new Windows 10 /
Office 2016 we have rolled out (we are not quite sure why).
So we have decided to venture down the path of using the newer method. The
newer method calls for using ".ODC" files which allow you to specify SQL
Querys in them and connect to any data source you want.
When we use this method against DB2 with Microsoft Word we get "Record 1
contained too few fields" when attempting to use the .ODC file to bring
data into a MS Word document.
.ODC file works fine pulling data into excel. Just not MS Word.
Here is the .odc file we attempted to use:
https://pastebin.com/14kDxF4z
Anyone get past the "Record 1 contained too few fields" issue?
midrange.com
