Home |
Search |
Today's Posts |
#1
Posted to microsoft.public.word.mailmerge.fields
|
|||
|
|||
Using HTML file as data source for Mail Merge
Hello
Have a problem here and I have not found anything about this on MS Office Support site. We use a generated HTML file as a datasource for the Mail Merge from our application. The problem arizes when the number of Merge Fields defined in the HTML file exceeds 63(!). After I open the datasource in Merge Document I can see only first 63 Merge Fields in the 'Insert Merge Field' dialog. And the 63rd merge field name is composed of the names of merge fields which come after the 62th field(!) However when I use the comma-separated file or an SQL datasource I do not experience any problems - I have tried with datasources with more than 100 fields. Do you happen to know what the problem may be? |
#2
Posted to microsoft.public.word.mailmerge.fields
|
|||
|
|||
Using HTML file as data source for Mail Merge
I think that you are probably running up against the limitation that Word
has on the number of columns in a table. For that reason, data sources created through the mailmerge wizard in Word XP and later are saved as .mdb (Access) files where the limit is 256 fields. -- Hope this helps. Please reply to the newsgroup unless you wish to avail yourself of my services on a paid consulting basis. Doug Robbins - Word MVP "thenin" wrote in message ... Hello Have a problem here and I have not found anything about this on MS Office Support site. We use a generated HTML file as a datasource for the Mail Merge from our application. The problem arizes when the number of Merge Fields defined in the HTML file exceeds 63(!). After I open the datasource in Merge Document I can see only first 63 Merge Fields in the 'Insert Merge Field' dialog. And the 63rd merge field name is composed of the names of merge fields which come after the 62th field(!) However when I use the comma-separated file or an SQL datasource I do not experience any problems - I have tried with datasources with more than 100 fields. Do you happen to know what the problem may be? |
#3
Posted to microsoft.public.word.mailmerge.fields
|
|||
|
|||
Using HTML file as data source for Mail Merge
Doug,
I have a related question to "thenin". Basically, I am researching the process to utilize the data on an html page in IE and perform a mail merge to a word document to create a letter. I did find one article in the KB http://support.microsoft.com/default...22120121120120 but was wondering if there are alternate or newer solutions which have been developed. thanks in advance for your help. -- David "Doug Robbins - Word MVP" wrote: I think that you are probably running up against the limitation that Word has on the number of columns in a table. For that reason, data sources created through the mailmerge wizard in Word XP and later are saved as .mdb (Access) files where the limit is 256 fields. -- Hope this helps. Please reply to the newsgroup unless you wish to avail yourself of my services on a paid consulting basis. Doug Robbins - Word MVP "thenin" wrote in message ... Hello Have a problem here and I have not found anything about this on MS Office Support site. We use a generated HTML file as a datasource for the Mail Merge from our application. The problem arizes when the number of Merge Fields defined in the HTML file exceeds 63(!). After I open the datasource in Merge Document I can see only first 63 Merge Fields in the 'Insert Merge Field' dialog. And the 63rd merge field name is composed of the names of merge fields which come after the 62th field(!) However when I use the comma-separated file or an SQL datasource I do not experience any problems - I have tried with datasources with more than 100 fields. Do you happen to know what the problem may be? |
#4
Posted to microsoft.public.word.mailmerge.fields
|
|||
|
|||
Using HTML file as data source for Mail Merge
Sorry, that is not something with which I have any experience. I suggest
that you start a new thread as that will be more likely to attract attention from others who may be able to help you. -- Hope this helps. Please reply to the newsgroup unless you wish to avail yourself of my services on a paid consulting basis. Doug Robbins - Word MVP "David" wrote in message ... Doug, I have a related question to "thenin". Basically, I am researching the process to utilize the data on an html page in IE and perform a mail merge to a word document to create a letter. I did find one article in the KB http://support.microsoft.com/default...22120121120120 but was wondering if there are alternate or newer solutions which have been developed. thanks in advance for your help. -- David "Doug Robbins - Word MVP" wrote: I think that you are probably running up against the limitation that Word has on the number of columns in a table. For that reason, data sources created through the mailmerge wizard in Word XP and later are saved as .mdb (Access) files where the limit is 256 fields. -- Hope this helps. Please reply to the newsgroup unless you wish to avail yourself of my services on a paid consulting basis. Doug Robbins - Word MVP "thenin" wrote in message ... Hello Have a problem here and I have not found anything about this on MS Office Support site. We use a generated HTML file as a datasource for the Mail Merge from our application. The problem arizes when the number of Merge Fields defined in the HTML file exceeds 63(!). After I open the datasource in Merge Document I can see only first 63 Merge Fields in the 'Insert Merge Field' dialog. And the 63rd merge field name is composed of the names of merge fields which come after the 62th field(!) However when I use the comma-separated file or an SQL datasource I do not experience any problems - I have tried with datasources with more than 100 fields. Do you happen to know what the problem may be? |
#5
Posted to microsoft.public.word.mailmerge.fields
|
|||
|
|||
Using HTML file as data source for Mail Merge
Hi
Yeah, I know about the limit of 256. But why in this case I only get 63 of them? And why only with an HTML data source? It is fine with other data source types. "Doug Robbins - Word MVP" wrote: I think that you are probably running up against the limitation that Word has on the number of columns in a table. For that reason, data sources created through the mailmerge wizard in Word XP and later are saved as .mdb (Access) files where the limit is 256 fields. -- Hope this helps. Please reply to the newsgroup unless you wish to avail yourself of my services on a paid consulting basis. Doug Robbins - Word MVP "thenin" wrote in message ... Hello Have a problem here and I have not found anything about this on MS Office Support site. We use a generated HTML file as a datasource for the Mail Merge from our application. The problem arizes when the number of Merge Fields defined in the HTML file exceeds 63(!). After I open the datasource in Merge Document I can see only first 63 Merge Fields in the 'Insert Merge Field' dialog. And the 63rd merge field name is composed of the names of merge fields which come after the 62th field(!) However when I use the comma-separated file or an SQL datasource I do not experience any problems - I have tried with datasources with more than 100 fields. Do you happen to know what the problem may be? |
Reply |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Forum | |||
How do I create a read-only mail merge data source? | Mailmerge | |||
Merge multiple data in one document from same data source | Mailmerge | |||
Specific Email Merge w/ Specific Attachements | Mailmerge | |||
mail merge using excel file as data source | Mailmerge | |||
Legacy Access2/VB4 app merge errors with Word 11 | Mailmerge |