If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
mail merge problem
I am using Office 2003. In my Access 2003 database, I have fields in one
table that are looked up from a separate table. When I try to merge the fields from the main table into a Word document, the Autonumber(primary) field is displaying in Word, not the field I want. In all of my forms and Data Access Pages, the correct field shows, but the Mail Merge is not working. Any suggestions? |
#2
|
|||
|
|||
mail merge problem
Your question would be more proper for the MS Word newsgroup.
However, in MailMerge, YOU select what fields to display in the letter. You have 100% control over which fields and where they show up. I suggest you look at the MailMerge HELP in Word for more detailed information. "rm51" wrote: I am using Office 2003. In my Access 2003 database, I have fields in one table that are looked up from a separate table. When I try to merge the fields from the main table into a Word document, the Autonumber(primary) field is displaying in Word, not the field I want. In all of my forms and Data Access Pages, the correct field shows, but the Mail Merge is not working. Any suggestions? |
#3
|
|||
|
|||
mail merge problem
This is one of the many problems and evils of using what we call lookup field. this issue's explained here a bit: http://www.mvps.org/access/lookupfields.htm This solution to the problem is rather simple, simply fire up the query builder, drop in the original main table, and drop in and join in the additional tables for the additional look up values that you need. You can then choose and drop in the description field and not use the ID fields as you are now. so the solution is to use a query in place of the table directly, and in the query at in those description feels that you need. The above is a perfect example as to why I avoid and do not use those look up fields. As you can see at the end of the day to your winding up to use SQL and writing this in the correct way that you should have done in the first place... -- Albert D. Kallal (Access MVP) Edmonton, Alberta Canada |
Thread Tools | |
Display Modes | |
|
|