Database Handicapping Software- JCapper

JCapper Message Board

          JCapper 101
                      -- Rebuild Data Base??

Home Register
Log In
By Rebuild Data Base??
6:38:05 AM
If I download all data to the (C:) drive and at the end of the year move all data off the (C:) drive, to an external drive and delete the data on the (C:)drive, do I have to rebuild the data base to retreive data off the external drive?

Hope this makes sence, mind is a little foggy this morning:LOL


7:51:01 AM

After all the data is compiled it goes in the starter history file , which will stay on your c drive..
I believe its OK to move your jcp and xrd files off the c drive.
I've done it , cause it takes mucho storage :))
and no need to rebuild

~Edited by: Caveat  on:  4/23/2015  at:  7:51:01 AM~

4:42:51 PM
Here's a link to an older thread that contains (I think) pretty much all of the relevant info:

"Your Work:

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.



--end quote


Copyright 2018 JCapper Software              back to the JCapper Message Board