[Peter Hibbs[_2_]]

Office 2003.

I am trying to create a Mail Merge document using Access for an
insurance broker. The data to be merged is in an Access table and
there is one record for each Customer/Policy . The problem is that
there may be more than one Policy for any given customer, so the data
in the table (simplified for this post) will look something like :-

Client Name Client Address Policy No Amount Due
-------------- ------------- ------------- -----------
Mr J Bloggs 34 High Street XYZ123456 £200.00
Mr J Bloggs 34 High Street ABC777999 £450.00
Mr J Bloggs 34 High Street Z12345T88 £823.00
Mr A Smith 64 Acacia Ave SM836464 £435.00
Mr A Smith 64 Acacia Ave SM0925337 £189.00

The records are sorted on customer surname and initials so will always
be grouped together like this.

The problem is that, if I just include the fields above in a standard
Mail Merge document, Mr Bloggs will receive three separate letters and
Mr Smith will receive two letters. What I need to do is to send ONE
letter to each customer and include the multiple lines of policy
information in the same letter.

So if the Mail Merge Master looks something like :-
____________________________________________
Title Initials Surname
CustomerAddress

The following policies are due for renewal this month -

Policy Number: PolicyNo
Premium Due: AmountDue
____________________________________________

The merged letter would then look something like :-
____________________________________________
Mr J Bloggs
34 High Street

The following policies are due for renewal this month -

Policy Number: XYZ123456
Premium Due: £200.00

Policy Number: ABC777999
Premium Due: £450.00

Policy Number: Z12345T88
Premium Due: £823.00
____________________________________________
Next letter for Mr A Smith follows here and so on :---


Is there any mechanism in Word that if certain fields are repeated in
a table, it will NOT create a new letter but still add the
non-repeated fields to the same letter. If not, is there any way it
could be done in the Access table,(I have complete control over what
is stored in the table). I'm sure this sort of thing must be fairly
commonplace in mail merge operations.

Peter Hibbs.