![]() |
#1
|
||||
|
||||
![]()
Hi
I've been asked to help one of my colleagues who is going to be receiving what is essentially a relational database from a client, but as a flat file, to be sent a letter with accompanying pages of tables with billing info. So he will get 8 fields of an address, followed by 22 fields of billing info for each bill referenced for this address. The example we've got is for 1 address with 65 different bill references, so it's a single row of data with 1438 fields, which is clearly bonkers! What's worse, they want each of the bill references (22 fields) to be on separate line of a table in a document. As far as I'm aware, you can't set up a merge to a table so that it adds a row for each set of fields that is occupied - you have to define the rows 'up front'. We can't put in the maximum number of rows as it would mean a lot of blank rows for those records with only a few bill references. Obviously inserting 1438 fields is going to take an absolute age and is impractical in itself. Could anyone suggest the best way to approach this problem? - needless to say going back to the client is not an option as this is the only way they can send the data to us. I do know some VBA and vb.net, so could do some macros to prep the data before the merge. I'm still a little stumped as to the best approach though. Any ideas? ........(please!) |
Tags |
merge data |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
![]() |
marym | Mail Merge | 3 | 04-09-2016 05:17 AM |
![]() |
sfkHooper | Mail Merge | 6 | 01-19-2016 04:24 PM |
![]() |
mdod | Word | 1 | 07-19-2013 06:33 PM |
![]() |
Aude | Mail Merge | 1 | 01-06-2012 07:38 PM |
![]() |
GeoB | Mail Merge | 3 | 09-08-2011 11:03 PM |