|--from the email inbox:|
"Hi Jeff!--end quote
I hope you can help me with something..
I'm working to build a database of just 2 racecourses: Tampa Bay and Santa Anita. I just downloaded the Jan-Feb HDW files for TAM and when I'm at the card loader, and try to load the files, this message appears:
And does the same for 24 of my 25 files. It just keeps on Folder 1 the first file. Then, when I finish closing all the error messages, this message appears:
But then I go to the PPs and as you can see, just one file was loaded.
I cleared all the scratches and it keeps happening. My questions are: Do I have to load day by day the cards? Is there a place where I can see all the cards loaded in each folder? Once that I load the card for day X, do I have to loaded again when I close the program and reopen it? I don't know what am I doing wrong, and I'm a bit confused.
Thanks in advance"
Your questions (above) appear to fall into two separate areas:
1. Loading Files into the program in order to run a Calc Races and generate same day race reports and PPs.
2. Building Databases
With that said, I'll try to address each of those areas separately --
1. Loading Files into the program in order to run a Calc Races and generate same day race reports and PPs:
It appears that you are trying to use either the DFM Card Loader or the original Card Loader to load every .JCP file for TAM into the program.
There is no reason to ever want to do this!
In fact the DFM Card Loader (and the original Card Loader) are programmed not to allow you to load more than one data file into the program for the same track code. The "TAM race card already loaded" message that you got is my way of telling you that trying to load multiple card files for the same track code into the program is something you never want to do!
The info model -- the purpose of the DFM Card Loader and the original Card Loader) is:
To enable you to load .JCP files for a single day into the program -- so that you can run a Calc Races for that single day -- and generate single day race reports and PPs for that single day -- so that you can play the races for that single day!
The next morning you would begin the cycle anew:
• You would download and process new race files for today -- bring up the DFM Card Loader -- use it to delete the previous day's data files from the program -- and load today's data files into the program.
• Then you would use Scratch BOT to get scratches and changes for today.
• Then you would use the Main Module to run a Calc Races for today's races.
• Then you would use the Report Viewer to look at an HTML Report for today's races -- and use the PPs Generator to look at PPs for today.
• And from there -- you might use the info on the reports to make a few informed decisions about today's races!
2. Building Databases:
Q. Do I have to load day by day the cards?
A. No. You do not (ever) load files into the program using the DFM Card Loader or the original Card Loader for purposes of running a Build Database Routine.
The only reason to load files into the program using the DFM Card Loader would be for purposes of running a Calc Races (see above.)
To run Build Database routines, I suggest reading the Building JCapper Databases Help Doc to get the relevant background info -- and from there, make your best effort -- working hands on with the program -- to follow the instructions in the help doc itself.
Cut and paste from the Building JCapper Databases Help Doc:http://www.jcapper.com/helpDocs/JCapper_BuildDatabaseHowTo.htmTo create a JCapper Database:
1. From the Main Module, click the Build Database button. This will launch the Database Builder.
On the Database Builder Main Screen:
1. Read the On Screen Instructions. They're there as a simple reminder so that you don't have to look here.
2. Select the appropriate Data File Type from the file types drop down. If are running JCapper under an HDW User License select HDW JCapper Data file (*.jcp) as your file type from the drop down. If you are using Brisnet files, select either Bris $1.00 DRF Single Format Data File (*.drf) or Bris Multicaps Data File (*.mcp) as your file type. Your file type selection will auto persist – making your selection the default until you change it. Note: Your file type selection must also match the Data Vendor Selection from the User System Definitions Screen. See the screenshot gallery below.
3. Use the Folder Icon to point to a target folder. This step is necessary only if your data and results files are sitting on a folder other than your default data folder. Hint: As a Best Practice, get in the habit of using the Data Folder Manager to set your Default Data Folder before launching the Database Builder. That way the Database Builder will auto point at your Default Data Folder every time you launch it.
4. Select the appropriate Build Mode from the Build Modes drop down. Hint: See the section on Build Modes below for an explanation about each build mode.
5. Click the Build Database button. This will cause the Database Builder to run the Build Database Routine. When the routine has been completed, you will be given a chance to view an exception report where you can see a listing of any missing XRD results files.
That's it. Those are the bullet points you need to know before building JCapper Databases… the high level look at the landscape… as viewed from 50,000 feet.
Hint: To see a demonstration of database builds in action, visit JCapper.com. Click the JCapper 101 Audio Video link
and look for the Index section labeled Building Databases.
Watching the videos there will help clear things up. They say a picture is worth 1000 words.
Of course you'll need to understand Build Modes first!
So read the section in the Help Doc beneath the headline that says "Database Build Modes (Added 4/27/2010)" to get the relevant background info.
And from there --
If you are operating JCapper in Playlist File Mode:
• Run your first build on any folder in Mode 1.
• Run (daily) builds after adding new files to a previously built folder in Mode2.
If you are operating JCapper in SQL Mode:
• Run your very first build on your very first folder in Mode 3.
• Run your first build on a newly added folder in Mode 4.
• Run (daily) builds after adding new files to a previously built folder in Mode 5.
~Edited by: jeff on: 2/15/2018 at: 9:24:53 AM~