home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
High Voltage Shareware
/
high1.zip
/
high1
/
DIR22
/
MMCONV15.ZIP
/
MMSORT.DOC
< prev
next >
Wrap
Text File
|
1993-09-15
|
5KB
|
136 lines
MMSORT
MMSORT is intended for people who have multiple MealMaster databases.
It allows efficiency in entering recipes to the appropriate database
initially without manual sorting. If combined with MMDRIVER which runs
from archived MealMaster files, running multiple databases can become
relatively convenient and storage efficient as well.
MMSORT gives you the following display when run without parameters:
Version 1.00 Meal-Master recipe sorter by Rodney Grantham
Usage: MMSORT infile
infile - contains MM format recipes to be processed
Sorting control information must be set up in the file MMSORT.PRM.
Each of up to 25 lines contains a list of associated categories.
The first category on a line will determine the filename.
Recipes with no matching categories go to XTRAmmdd.n.
CONFIG.SYS must have FILES= set high enough.
Can't open recipe file:
-----------------------------------------------------------------
Basically, you just provide a file of MealMaster format recipes as the
input to MMSORT. The default file MMSORT.PRM can be used in sorting these
recipes. You can either modify it or define a totally new file to control
processing. If it is missing, MMSORT will inform you.
The first name on a line in MMSORT.PRM is used to create a file name
and the file is opened. If a file name duplicates a former one, that line
will be skipped. The file name will be qualified with .IN. If it already
exists, the program appends to it. At the end of the run files that had
data added to them are displayed with number of recipes and number of lines
written. Since MM exports with an extra space between recipes, the number
of lines totals will not match. Number of recipes should match.
Sample run:
MMSORT mm.out
Processing: mm.out
Processed: mm.out
Recipes saved: 1725
Lines read: 57168
1056 recipes ( 37063 lines) written to XTRA0914.3 from mm.out
16 recipes ( 466 lines) written to CROCKPOT.IN from mm.out
64 recipes ( 2334 lines) written to SOUPS.IN from mm.out
1 recipes ( 24 lines) written to DOGS.IN from mm.out
19 recipes ( 639 lines) written to PASTAS.IN from mm.out
131 recipes ( 4449 lines) written to APPETIZE.IN from mm.out
204 recipes ( 6013 lines) written to PRESERVE.IN from mm.out
211 recipes ( 3743 lines) written to BEVERAGE.IN from mm.out
23 recipes ( 672 lines) written to MISC.IN from mm.out
The matching process is not perfect. For example the category "Rock
Spring" in one recipe put the recipe in Crockpot. 'ROCK' matched with
'ROCK' in cROCKpot.
If you were to put CHICKEN on the first line, then an APPETIZER with
CHICKEN in the category line would end up in the first line group rather
than the later APPETIZER category it also matched. So ordering of category
lines can affect your outcome.
In setting up MMSORT.PRM, use plurals for category names. This will
match with either singular or plural categories. It is not necessary to
have both DESSERT and DESSERTS - DESSERTS will catch both. Case is
irrelevant. MMSORT will upper case everything for matching purposes.
Up to 220 characters are read in for a category line. But you can make
several smaller lines for what will end up as one file and you will
then have several input files to load. However, only 25 category lines are
supported.
Files are opened 'append'. Repeated runs will continue to add to the
same files unless they are purged or renamed. This is unlike the behavior
of most of my programs. The XTRAmmdd.n is handled as usual with successive
versions being numbered. This supports the usage described below.
If you have a lot of category lines, lots of files are opened
simultaneously. This may require changing your CONFIG.SYS FILES= statement
to support the additional files needed. Alternatively, you can sort the MM
recipes in successive passes. Each time you would use the XTRAmmdd.n file
from the prior run as input to the next.
If you normally run with archived recipe databases, you may find that
exporting a large database and processing it severely impacts your storage.
In testing, I finally realized some of the errors I was encountering were
because I was down to zero available storage.
If there are too many files for the parameters set in \CONFIG.SYS or
you are out of storage, you will receive the following message on the file
that exceeds the limit:
MMSORT mm.out
Processing: mm.out
XTRA0914.1 - couldn't open Error 0
Possibly exceeding maximum permitted files.
Also possible that your storage is exhausted.
This should be packaged with MMCONV, MARKIT and MSGSPLIT. Or with
MMDRIVER.
Like MARKIT and MSGSPLIT, it is essentially a free inclusion. If you
benefit from it, register MMCONV and/or MMDRIVER. If the utilities are
particularly useful and you would like to encourage additional ones,
include a little extra with your registration.
Rodney Grantham
770 Cranberry Trail
Roswell, GA 30076