No merging of graphics is required in this solution, but it only works in those cases where the graphic is the same for all instances of the merged data on a page. If this is not feasible, you can just not worry about merging the graphics, but put them "in place" in the Word document. The most obvious workaround is to not use Access, but instead use a Word document as your data source. Since there can't be a solution, there needs to be a workaround. The problem doesn't exist between two Word documents because a different type of communication channel is used. This makes sense, since the cause of the problem is the DDE communication channel between Access and Word. This problem, by the way, is not evident if you are using another Word document as your data source. It is entirely unclear why Microsoft didn't use OLE Automation instead, which could have solved the problem.
It appears that Word uses DDE to communicate with Access, and DDE is unable to transfer OLE objects (like the graphic) across the DDE interface. When the question was put to our astute readers, we found out that it didn't work because it can't. One WordTips reader wrote that he was having a problem merging OLE graphic objects from an Access table field into a Word document.
One such bump is evident when using an Access table as the data source for a Word mail merge. This is not to say there aren't "bumps" in the road to blissful co-existence, however. One of the big benefits to using Microsoft Office is that the programs in the suite all work together.
0 kommentar(er)
