November 2004
Handling
Duplicates and Failed Recipes During Recipe Import
How
to work with duplicate recipes during recipe import
During the import only the recipe name is checked to determine
duplicates. If you want to see all the duplicate recipes on import, then
turn off the import dupe check (Tools… Options… Import/Export
tab… uncheck “duplicate checking”) and import the recipes
into a new cookbook. Then you can do a
manual dupe check by opening recipes with like name, or use the Dupe
Check… button on the recipe selection window, which will check more than
just the name to determine duplicates.
We recommend that you do all imports into a new cookbook, then use this cookbook to touch up the recipes as needed
before you distribute them to your permanent cookbooks. This way you can delete recipes you
don’t want, and you can handle duplicates as you wish. You can also check and change recipe
categories to suit your preferences. You
can then distribute the imported recipes into your permanent cookbooks using
File… Export Recipes… [to an NYC cookbook].
How to work
with recipes that failed the import process
During a recipe import, any recipes failing to import are collected in a text file. This file has an “.emx” extension. You can open these files with an editor (File… Run Text Editor… or hit the Text Editor toolbar button), and make changes and then try to reimport them. These “.emx” files will build up over time because almost every import you do will create one. You can delete unwanted “.emx” files using Tools… Data Management… Import/Export tab… delete files containg failed imports.
home | overview | download | features | screenshots | purchase | support
tips
| FAQ | recipes | postcard | more links | email us