Midori Media > Products > myPM Merge Midori Media
Home Products Downloads Order Support Links Contact Us
myPM SCG myPM Replicate myPM Update myPM Merge      
Overview Features Requirements Operation Pricing History FAQ
General FAQ Installation FAQ Registration FAQ Configuration FAQ Process FAQ

myPM Merge: Configuration FAQ

WHAT IS A MERGE DEFINITION?
A Merge Definition defines the configuration settings required to generate a Merge Document or Workbook from data stored in a MS Access Database or MS Excel Workbook. Define a Merge Definition for each merged Document / Workbook you wish to generate. You may group common Merge Definitions in the same myPM Merge Data File. ( *.mmu )

WHEN BROWSING FOR FIELDS, myPM MERGE DOES NOT DISPLAY THE CORRECT FIELD DESCRIPTION. WHY?
myPM Merge extracts field descriptions located in the row immediately above the First Row, as defined on the Merge Source Tab.
Ensure the First Row is set to the first row in the Worksheet that contains data.

WHAT IS THE PRIMARY KEY FIELD?
The primary key field is a field in the Source File used by myPM Merge to determine which records to process.
Records containing a blank Primary Key Field value are ignored by myPM Merge.
The Primary Key Field should be set to a source field that contains a value for each source record.

HOW CAN I CONFIGURE myPM MERGE TO IGNORE DUPLICATE RECORDS.
Enable the Ignore Duplicate Primary Key Records option, located on the Merge Source Field.
If two or more source records contain the same primary key field value, only the first record is processed by myPM Merge.

CAN myPM MERGE SAVE EACH DESTINATION FILE TO A DIFFERENT FOLDER?
Yes. To achieve this, define the path for each file in the Source Field containing the save filename.
( eg. Folder_A\File_01.doc, Folder_B\Folder_C\File_02.doc, etc. )

WHAT IS A MERGE MAP?
The Merge Map defines the relationship between Source Fields and Destination BookMarks or Cells.
Use the Merge Map to define which source record fields should be inserted in the Destination File.

DO I NEED TO ENTER A DESCRIPTION IN THE MERGE MAP FOR EACH ENTRY?
No. The Description Field is provided so that you can enter a meaningful description for the source field.
It is not used by myPM Merge, and thus can be left blank.

HOW DO I INSERT THE SAME SOURCE FIELD MORE THAN ONCE IN A MS WORD DOCUMENT?
Method A.
Insert MS Word fields at the second and subsequent locations where the source field value is to be inserted.
The field code should be set to: REF BOOKMARK, where BookMark is the name of the BookMark that defines the location where the first source field value is to be inserted.
Method B.
Define multiple BookMarks for each location where the source field value is to be inserted.
An entry for each of these additional BookMarks will need to be defined in the Merge Map.

HOW DO I INSERT THE SAME SOURCE FIELD MORE THAN ONCE IN A MS EXCEL WORKBOOK?
Method A.
Define a formula in the second and subsequent Cells where the source field value is to be inserted.
The formulae should be set to: =A1, where A1 is the name of the Cell where the first source field value is to be inserted.
Method B.
Define multiple entries in the Merge Map, one for each Destination Cell.

WHAT IS A MERGE FILTER?
The Merge Filter determines which source records should be processed by myPM Merge.
Only source records that meet the defined Merge Filter criteria are processed.

HOW DO I CONFIGURE THE MERGE FILTER TO IGNORE BLANK FIELD VALUES?
Select the "Is not blank" comparison for the appropriate source field in the Merge Filter.
Only records that contain a value for the defined field will be processed by myPM Merge.

WHAT IS A MERGE PREVIEW?
The Merge Preview defines which source record fields are displayed in the Merge Preview Dialogue.
Select appropriate fields that enable you to easily select which records to merge.

DO I NEED TO ENTER A DESCRIPTION FOR EACH MERGE PREVIEW ITEM?
No. If you do not enter a description, myPM Merge will display the Source Field name in the Merge Preview Dialogue.


Copyright © 2003 - 2004 Midori Media - All Rights Reserved Privacy Policy Feedback Version 2.4.0.0 20 September 2004