View Single Post
 
Old 05-18-2019, 07:07 AM
B-Man B-Man is offline Windows 7 64bit Office 2013
Novice
 
Join Date: May 2019
Posts: 5
B-Man is on a distinguished road
Default

Quote:
Originally Posted by macropod View Post
It seems you want the table to change when the Kart changes. In that case you need to use the Kart field as a key - possible as the second in a pair of keys.

To see how to do so with any mailmerge data source supported by Word, check out my Microsoft Word Catalogue/Directory Mailmerge Tutorial in the 'Sticky' thread at the top of this forum:
https://www.msofficeforums.com/mail-...-tutorial.html
or:
http://www.gmayor.com/Zips/Catalogue%20Mailmerge.zip
The tutorial covers everything from list creation to the insertion & calculation of values in multi-record tables in letters. Do read the tutorial before trying to use the mailmerge document included with it.
Sorry I didn't have time to do an actual mail merge before to show what it does vs what it should. But have now (linked below) Its the entry field that changes not the kart.

Quote:
Originally Posted by macropod View Post
Depending on what you're trying to achieve, the field coding for this can be complex. However, since the tutorial document includes working field codes for all of its examples, most of the hard work has already been done for you - you should be able to do little more than copy/paste the relevant field codes into your own mailmerge main document, substitute/insert your own field names and adjust the formatting to get the results you desire. For some worked examples, see the attachments to the posts at:
https://www.msofficeforums.com/mail-...html#post23345
https://www.msofficeforums.com/mail-...html#post30327
I will check these out and see if it's of any benefit.

Quote:
Originally Posted by macropod View Post
Another option would be to use a DATABASE field in a normal ‘letter’ mailmerge main document and a macro to drive the process. An outline of this approach can be found at: http://answers.microsoft.com/en-us/o...1-1996c14dca5d
Conversely, if you're using a relational database or, Excel workbook with a separate table with just a single instance of each of the grouping criteria, a DATABASE field in a normal ‘letter’ mailmerge main document could be used without the need for a macro. An outline of this approach can be found at:
https://answers.microsoft.com/en-us/...f-8642e46fa103
For some working examples, see:
https://www.msofficeforums.com/mail-...-multiple.html
https://www.excelforum.com/excel-gen...ml#post5110813

The DATABASE field can even be used without recourse to a mailmerge. An example of such usage can be found at: https://www.msofficeforums.com/mail-...html#post67097

Alternatively, you may want to try one of the Many-to-One Mail Merge add-ins, from:
Graham Mayor at http://www.gmayor.com/ManyToOne.htm; or
Doug Robbins at https://onedrive.live.com/?cid=5AEDC...43615E886B!566

Heres what it does vs what it should
https://www.dropbox.com/s/pf71npyosv...erge2.PNG?dl=0


The macro and Mail Merge are fine i think its a bug in the way it handles numbers not letters or im missing something simple.

Other classes have duplicate front letters and work fine ie.
'KT Light', 'KT Medium', 'KT Heavy', 'KT Twin'. also other classes with numbers '100' and '200' work fine
but '125 Light' and '125 Heavy' seem to merge.
If i change it to '125 Light' and '126 Heavy' it works as it should. but alas they are both a '125' class

its taking the numbers as the field calling it a duplicate so not separating them and ignoring the letters behind it. So testing any class by putting 125 in front ends up merging them into the 1 table.
Reply With Quote