I have to be honest after waiting years to be able to bring my Q&A into the modern ages with Sesame, i still havent used Sesame.  The mailmerge issue has always been my main concern. We have a number of staff that uses dozens of differnt legal forms all day. Once i read the dozen"simple" steps to do a mail merge or the even easier 9 steps I had thrown up my hands in frustration.  Q&A takes about two steps and is perfectly integrated. Now I see there is a sesame utility that is supposed to make mail merge easier? Only pay an addition fee for something that should be part of the program..and while you are at it if you actually want to use the utility you might also want to pay for an addtional user license.  Is there something wrong with this picture or am i just getting crochety in my old age.  I am an end user and had hoped that even though sesame has more power than Q&A that it would also retain some of its simplicity.
rb ???

Sesame has an excellent tool called ODBC!.

ODBC is a tool that allows many other programs to "link" directly into a database.  Lantica has provided Sesame with the necessary ODBC driver.  At this time it is a Read-Only tool, but that is all you need for Mail Merges.

No exports
No imports
No utilities.

Start your Sesame Server, no need to open a client.
Open Merge document in word processor (Word, OpenOffice, eg.).
Filter records if desired (like you did in Q&A)
Merge document with data source.
Preview results, edit document as needed (or not).
Save/Print/Email,,,,, whatever you want..
DONE!

You can make macros in your word processor to do some of these tasks if you do not want to take the few manual steps.  Like all merge documents, setting up the master will take a few minutes, but then you have it forever.

Just as you saved Merge Specs in Q&A, you can save Merge Specs in your ODBC queries.  Make them once, then use them forever, or edit as needed when using them.
===========================

I never see any postings on ODBC so I often think that I am the only one who uses this.  After an ODBC connection is defined, you are done.  There were some issues with initial documentation and connections, but I have not seen any problems since version 1.0.3.