Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
DiscussionsAccessExcelInfoPathOutlookPowerPointPublisherWord
DirectoryUser Groups
Related Topics
Outlook ExpressInternet ExplorerWindowsMS Server ProductsMore Topics ...

MS Office Forum / Word / Mailmerge and Fax / August 2006

Tip: Looking for answers? Try searching our database.

merge query criteria error bugs !!!

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
K.C. Ho - 31 Aug 2006 03:18 GMT
I find a bug in office 2003,

When I am using Word 2003 to have a merging with Excel 2003,
I selected 2 criteria, "Date" = "0829", and "Eng_verison" is blank (or is
not equal "YES")

It is no problem after the filter runs, the little excel show perfect
information i need. The total no. of record is about 300 which is i wanted.

but when i press ok and wait the merging, the no. of record suddenly goes to
3000 and then i went back to check the filtering. Strange !! There are one
more criteria that "Eng_version" is blank ! which means two of the same
criteria !But it use a "OR" to link with my other criterias.

It is so annoying that my main job in company is to merging letters. It may
have to solve by upgrading by it is already office 2003. Could you please
give me some other ways first ?
Peter Jamieson - 31 Aug 2006 11:40 GMT
You are correct that Word sometimes adds query criteria that should not be
there.

You may find that changing the way that Word connects to Excel is enough:
a. check Word Tools|Options|General|"Confirm conversions at open"
b. go through the process of connecting to your spreadsheet again
c. choose the DDE option when prompted.

In this case, you will be connected to the first sheet in the workbook, or
possibly the last sheet you had open.

This may be enough because Word uses your filter criteria to build an SQL
query, and it does this differently for different connection methods and
data sources.

Be aware that DDE is "deprecated" and ideally you would not have to use it.
Unfortunately, there are so many problems in this area that it is still
sometimes the best method to use.

Another approach would be to set up a VBA routine to do the connection, and
learn enough SQL to set up the criteria you want. Then you just change the
SQL and run the routine. I can go through that if you want.

Peter Jamieson

>I find a bug in office 2003,
>
[quoted text clipped - 16 lines]
> have to solve by upgrading by it is already office 2003. Could you please
> give me some other ways first ?
 
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.