Thanks for your very fast reply. However, it does not solve my problem. I want each record - including table, editable before finishing. I can see that I will have to generate the table as a field in my source data. Just a BIT of VBA pre-processing. The original table approach with DATAFILE would have been read only, if it had worked.

But there is a curly one, why does the manual Update Field command update the current record's table values and is there any VBA which really detects change of record, enabling a VBA, update of the table - for that record?

If I add the standard "before or after mailmerge routine to the VBA, it does NOT fire up when there is a change of record BUT does - for every record in the merge set, when I do the manual Update field for the table/database instance.

I still think that I will need to create the table value(s) into the original merge dataset.



Thanks, Michael

That simply isn't possible - neither mailmerges in general nor DATABASE fields in particular - permit that. What's the objection to doing the edits post-merge?

__________________
Cheers,
Paul Edstein
[Fmr MS MVP - Word]

Thanks "macropod".

I understand - a typical record set would be less than 10 - in the merge set.

The process would be

Start merge
Change non-table/database fields and layout for particular exercise.
Finish merge into separate docs and modify (no longer linked) table info on each as required.

Will work - but if the non-table fields needed further change - the whole modify table approach would be overwritten. The "further change" scenario is very likely.

As Malcolm 1 quoted, "Life wasn't meant to be easy"

Michael

If your mailmerge main document is properly formatted and you use the appropriate query parameters and field coding, there shouldn't be any post-merge editing to do.

I have no idea what you mean by:

__________________
Cheers,
Paul Edstein
[Fmr MS MVP - Word]