Quote:
Originally Posted by Abacus1234
I don't understand why I have to have a Mergefield in the WHERE clause. Also, when I try it through Quickparts it does not select the fields that I ask for. I have attached what the final report looks like. Thanks.
|
Since you've been describing the process as one that uses mailmerge and you referred to the need to incorporate 'a multi-record table', I assumed the table you wanted to generate varied according to a condition applicable to whichever record is being merged. In that case, the DATABASE field needs to perform that test. I'm not surprised that you can't accomplish this using Insert|Quick Parts|Field, as what's being done here is rather more than that tool was designed for. You could get further via Mailings|Insert Mergefield and Mailings|Rules, but even those probably won't go the distance - in which case you'll need to create the fields manually, using Ctrl-F9 to create the field braces and typing the relevant expressions between them. Of course, all this is moot if my assumption was wrong.
Indeed, the table in your latest attachment looks as if it's a standard one in which just the values change and the data all relate to a single record. In that case, you don't even need a DATABASE field. You should be able to do the lot via IF fields and MERGEFIELDS alone.