To use the template files:
-
download the files from the MCSL website to any directory.
-
double click on the mm-zips04.zip file and a window will pop up showing the contents of the
zipped template file.
-
click the 'extract' menu item.
-
Select the c:\swmeets directory and extract the files.
-
Repeat the above 3 steps for the tm_zips.zip file and extract the contents to the
c:\TMIIdata directory.
The template files (mm-zips03.zip & tm_zips.zip) contain the following files:
- week-x-2004.mdb there are 5 of these files. These files are
meet manager databases for each of the dual meets.
- DivRelay04.mdb this is the meet manager database for relays
- Divisionals2004.mdb this is the meet manager database for divisionals
- mcsl04-s.rec this file contains the current MCSL records that
can be imported into a meet manager database. The
above meet manager databases already contain these
records, so you typically will not need this file.
- MMmmddyy.HYV there are 6 of these files. These are event files
that you should import into your Team Manager
database which will create meets in your database
for each of the dual meets & divisionals.
You will use these meets defined in your Team Manager II
database in order to create entries for those meets.
MDB Files
HYV files
This year there is not a template Team Manager database that a team will start with for
the season. Instead you should do the following to setup your Team Manager for the new
season:
Create a new Team Manager II database
Export your swimmers & best times (if desired) from last year's database
Import the swimmers/times into the new database
The .HYV files should then be imported into the new Team Manager II database.
Do this by selecting 'file->import->meet events'.
Choose 'c:\TMIIdata' (where you extracted the files).
Select one of the .HYV files and click OK.
The meet will be imported and all of the events for the meet defined.
Repeat the above for all 6 files.
If you have any problems or questions, please contact someone on the Automation Committee
that is listed in the front of the MCSL handbook, or look here.
MCSL Automation Committee