JCapper Message Board
|| File space
|Question about saving files. |
Do we need to keep in the JCapper.exe file all the jcapper2.mdb saved files? I currently have 22 saved files in my exe file. Or can we clear up file space by deleting those files?
Also, can we clean up file space in jcapperbuild file by deleting older jcapper platinum downloads and only keeping the latest?
Or does this affect JCapper performance?
Your work is contained in the following 2 .mdb files:
This file contains your UDM definitions as well as definitions for UserFactors and UPR.
This file contains your sql factor setup and definitions for your sql html report. This file also contains starterhistory table data... crucial if you are using the Data Window to perform R&D in sql mode.
Note that JCapper requires both of these files be present. Both must be in the path locations specified above in order for JCapper to run.
If you value your work (it's the one thing I can't replace for you) I strongly recommend making regular backups of these two files.
Data and Results Files:
All data and results files downloaded from your data vendor are sitting on whatever target folder you downloaded them to.
Files generated by build database routines:
A file named pl_profile.txt is created on each target folder and is written to each time you run a build database routine. Although this file is crucial because it is the file the Data Window uses as a source whenever you are performing R&D in playlist file mode - it is 100% replaceable provided your data and results files are still sitting on the target folder and your are willing to run a build database routine on that target folder from scratch.
Data and results files from past years:
At some point, you have to decide when, past data becomes stale. For me that point is about 2 years. If you are thinking about removing anything JCapper related from a hard drive, consider moving entire target folders of older data (pl_profile.txt files included) onto CDs, flashdrives, another machine, or all three. CDs can be delicate. If you are using CDs it might be a good idea to burn 2 CDs for each old target folder that you remove from your hard drive.
JCapper Program Files:
Best to leave everything in the c:\JCapper, c:\JCapper\Exe, and c:\JCapper\Ocx folders fully intact. If you delete an .exe file it is very likely that you deleting a JCapper module (which won't be there for you when you decide to click its launch button.)
The c:\JCapperBuild folder:
Very early on I adopted the info model of asking JCapper users to download everything JCapper related to the c:\JCapperBuild folder. That way, in the event a user reports that something isn't working, I have a consistent place to look first when helping that user straighten things out.
When you download the download package file for a new program update (hopefully) you save it to the c:\JCapperBuild folder.
From there, when you double click it to run the extractor, the extractor copies new JCapper program content to the c:\JCapper, c:\JCapper\Exe, and (sometimes) the c:\JCapper\Ocx folder.
True, that info model results in JCapper having a larger footprint than it otherwise would if my goal were to keep the program's footprint to a minimum. (You end up with duplicate JCapper module .exe files sitting on your c:\JCapperBuild folder.)
In all seriousness thoough, when compared to videos that we all download, music and image files too, games, temp copies of web pages visited (that are auto saved to the hard drive without most of us even being aware) Windows updates, Adobe updates, security updates for this and that, hundreds of new programs installed on a whim, etc. JCapper's footprint on a modern hard drive is negligible.
Translation? If you are running out of hard drive space, chances are JCapper isn't causing the problem.
Ok, enough already with the program author rant thing.
Hint: If you ARE running out of hard drive space, I recall seeing a very good thread on that topic (2-3 months ago) in the computer section over at paceadvantage.
Older program download packages:
If you regularly download each new program update, and hopefully save them to your c:\JCapperBuild folder when you do, then after a few of years if you look at your c:\JCapperBuild folder you'll see all those older JCapper program download package files taking up space.
So far, and JCapper is in its 8th year, every single new program update that I've published is 100% backwards compatible with all of its predecessors.
For that reason, I can't see any reason whatsoever to keep older JCapper program download packages sitting on your c:\JCapperBuild folder around - especially when the latest program update is working error free.
Ok, enough already with the program author rant thing.
I'll say this: It isn't a bad idea to keep say the 3 to 4 most recent ones around just in case I f*ck up and introduce some un-fix-able bug into a current download package (and then fall off the face of the earth)... If that ever happens to me (stranger things have happened, right?) you can revert back to the last good known program update easily enough by double clicking that download package and running its extractor.
So yes, older JCapper program download package files CAN be deleted from the c:\JCapperBuild folder.
There you have it.
~Edited by: jeff on: 9/21/2011 at: 8:49:00 PM~
|Thank your for response Jeff.|
I do weekly and/or bi-weekly back up on external storage sticks of jcapper.mdb and jcapper2.mdb file.
I have regularly downloaded and always saved platinum updates to jcapperbuild file.
All aspects of JCapper working well. Just seems like this program keeps getting better and more interesting. It does reward work from data window.
Once again thank you for your prompt reply. The author is certainly permitted to proudly rant :)
"Q. Jeff - What about the 'raw' files downloaded from HDW? After building .JCP and .XRD files can I delete these? Or do I need to keep them?"--end quote
First, some background info about the 'raw' files downloaded from HDW:
What: One zip file per race card. Contains individual binary format race files (one file per race.)
File naming schema: First 2-3 characters indicates track code. Middle characters indicates month and day of month. Last 4 characters of zip file is J.ZIP. 'J' character indicates file contains past performance data. File extension (.zip) indicates this is a zip file.
Binary Race Files
What: File format is binary. One file per race.
Naming Schema: (Example file name: 1020j09.KEE) First 4 characters indicate month and day of month. 'J' character indicates file contains past performance data. File extension (.KEE) indicates track code (Keeneland.)
What: One file per race card. Each F.ZIP file contains one HDW Text Chart Results File.
Naming Schema: (Example file name: KEE1019F.ZIP) First 2-3 characters indicates track code. Middle characters indicate month and day of month. 'F' character indicates file contains results data. File extension (.zip) indicates this is a zip file.
HDW Text Chart Results File
What: This comma delimited text file contains a complete set of charts for one race card. Format is comma delimited text. Field mapping is linked to in the 'sticky' Data File Structure thread at the top of the private area of the JCapper message board.
Naming Schema: (Example file name: KEE1019F.TXT) First 2-3 characters indicates track code. Middle characters indicate month and day of month. 'F' character indicates file contains results data. File extension (.TXT) indicates this is a text file.
Where downloaded: In all cases, you will find the above 'raw' HDW files on the folder you had persisted/checked as the current active data folder in the DFM at the time you used JCapper's HDW File Download Tool to download these files from the HDW site.
Q. After using these files to build .JCP and .XRD files (which is what JCapper runs on) can the 'raw' HDW files be deleted?
A. Short answer: Yes.
Long answer: Unless you are really pressed for hard drive space, you might want to hold onto them. I am always worlking on getting new features into JCapper. (The raw HDW files contain a wealth of info that hasn't really been tapped yet.)
A likely scenario is that at some point in the future I will publish a new JCapper program update that makes use of some valuable piece of info contained in the raw files but not previously being inserted into .JCP or .XRD files.
If and when that happens, rebuilding older .JCP and/or .XRD files would enable you to get the new info into a JCapper database... Yet, rebuilding older .JCP and/or .XRD files to enable you to get the new info into a JCapper database is possible ONLY if you decided NOT to delete the 'raw' HDW files from your data folders.
Another likely scenario is that you are doing some database work of your own outside of JCapper. The HDW Text Chart Results file contains ALL of the info found in an official chart. By deleting the 'raw' HDW files you are deleting YOUR ability to bring info found in an HDW Text Chart Results File (but not an .XRD file) into the work you are doing outside of JCapper.
Hope I managed to explain most of that in a way that makes sense.