Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / New Users / December 2007

Tip: Looking for answers? Try searching our database.

mail merge problem

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
rm51 - 03 Dec 2007 17:00 GMT
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?
Dennis - 03 Dec 2007 18:04 GMT
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.

> 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?
Albert D. Kallal - 03 Dec 2007 19:30 GMT
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...

Signature

Albert D. Kallal    (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@msn.com

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.