Database Handicapping Software- JCapper

JCapper Message Board

          General Discussion
                      -- IMPORTANT REMINDER - New Year - Folder Structure -

Home Register
Log In
By IMPORTANT REMINDER - New Year - Folder Structure -
jeff
12/31/2014
2:04:14 PM
It's that time again. (Time to create folder structure for the coming new year.)

One of the things you NEVER want to do is mix and match files from different years on the same folder. The file names of data and results files that you download do not contain a year element.

Unless you create (and use) folder structure for the new year:

Not only do you run the risk of overwriting 2014 files with 2015 files... But you also risk corrupting your 2014 databases in the event you run a db build using a 2014 data file and a 2015 results file (or vice versa) for file names involving the same track code, month, and day of month.

I (personally) use a single folder for each year with 4 separate sub folders (one per calendar quarter) and 2 additional sub folders (to facilitate breaking up my race day into multiple groups in the DFM Card Loader.)


My old 2014 folder structure looks like this:

C:\2014
C:\2014\Q1_2014
C:\2014\Q2_2014
C:\2014\Q3_2014
C:\2014\Q4_2014
C:\2014\Folder2
C:\2014\Folder3


My new 2015 folder structure looks like this:

C:\2015
C:\2015\Q1_2015
C:\2015\Q2_2015
C:\2015\Q3_2015
C:\2015\Q4_2015
C:\2015\Folder2
C:\2015\Folder3


For the next several days, I will be toggling folders back and forth inside the DFM being EXTREMELY careful that all 2014 files are saved to my C:\2014\Q4_2014 folder - and that all 2015 files are saved to my C:\2015\Q1_2015 folder.




Year end is probably a good time to check the file size of your c:\JCapper\Exe\JCapper2.mdb file. The max size for any .mdb file allowed by Windows is 2.0 gigabytes (2000 mb.)

If you are at 1.5 gigabytes or larger it's probably a VERY good idea to bite the bullet now and rename your c:\JCapper\Exe\JCapper2.mdb file to something like c:\JCapper\Exe\JCapper2_YE2013.mdb - which serves to 1. Get the file out of the way and 2. Archive the file in such a way that you can connect to it using the Data Window MENU.

From there navigate to your c:\JCapperBuild folder, find the fresh blank copy of the JCapper.2.mdb file put there by the installer (filename: c:\JCapperBuild\JCapper2.mdb) and copy that file to your c:\JCapper\Exe folder. (Important: Make sure that you complete the file rename process first!)

From there use the JCapper2 Import Module to import the sql factor setup and html report layout out of your old file into your new file - and at this point your're all set for the new year.

Note: Here's a link to an older thread titled JCapper2.mdb file - what you need to know that contains comprehensive background info about folder structure and managing JCapper2.mdb files:
http://www.jcapper.com/MessageBoard/TopicReader.asp?topic=1340&forum=JCapper%20101





-jp

.


Reply
Caveat
1/1/2015
11:30:39 AM

So bottom line is...
when we create a new jcapper2 file ....using the data window is pretty much done for a while till it builds up..

Unless...

In my case , I have data from July 2012...

Start a new folder with all jcp and xrd files going back to Jan 2013 and rebuild database...

Correct?

Mike


Happy New Year to all

~Edited by: Caveat  on:  1/1/2015  at:  11:30:39 AM~

Reply
jeff
1/1/2015
9:31:46 PM

--quote:
"when we create a new jcapper2 file ....using the data window is pretty much done for a while till it builds up.."
--end quote



My reply:

No. Not at all.

In the Data Window:

1. Click MENU.

2. Select Connect to JCapper2.mdb File.

3. A dialog box will come up that enables you to connect to any existing (archived/backed up) JCapper2. mdb file (on any drive or folder) on your local machine or network. Simply use the dialog box interface to select and open the JCapper2.mdb file that you want.

From here, you can execute sql queries/sql UDMs in the normal manner against the StarterHistory Table in the connected to JCapper2.mdb file.

Hint: The Data Window dispalys the full path to the connected to JCapper2.mdb file as part of the results display.

(So if you are connected to an archived or backed up copy of a JCapper2.mdb file - you'll know at a glance.)

Hint: A Connection to an alternate JCapper2.mdb file opened in this manner is valid in the Data Window only - and terminates when you either: A. Use the Data Window Menu to connect to another JCapper2.mdb file or B. Exit the Data Window.

Hint: Connections to alternate JCapper2.mdb files opened in the Data Window using the Data Window MENU's Connect to JCapper2.mdb File option do not change in any way which JCapper2.mdb file is used by the Main Module during Calc Races and Build Database routines.

(In normal program operation the connected to JCapper2.mdb file in Main Module Calc Races and Build Database routines is always the c:\JCapper\Exe\JCapper2.mdb file.)


-jp

.



Reply
jeff
1/2/2015
1:22:13 AM

--quote:
"In my case , I have data from July 2012...

Start a new folder with all jcp and xrd files going back to Jan 2013 and rebuild database...

Correct?"
--end quote



Absolutely not correct.

No need to rebuild older databases from scratch.

To query older archived databases:

Connect to any archived JCapper2.mdb file through the Data Window MENU's Connect to JCapper2.mdb File option - and from there execute sql queries in a normal manner.

You do, however, continue to run Build Database routines on your current active JCapper2.mdb file only as new data and results files are added to your current active data folder.


-jp

.




Reply
Caveat
1/2/2015
9:42:25 AM

Whew...

Thxs Jeff...saved me a lot of time

:)

Mike

I have 2.5 years of data which made my jcapper2 file at 1.4 gigs
This comes out to 5.6 mb per year...
Looks like I need to start a new DB..:(


~Edited by: Caveat on: 1/2/2015 at: 9:39:51 AM~

~Edited by: Caveat on: 1/2/2015 at: 9:41:10 AM~

~Edited by: Caveat  on:  1/2/2015  at:  9:42:25 AM~

Reply
SILVER01HDW
1/2/2015
12:26:21 PM
Happy New Years...

Jeff, due to the size of my JCapper2.mdb file it was time to rename it... I went into my c:\JCapper\Exe\JCapper2.mdb file and renamed it to c:\JCapper\Exe\JCapper2_YE2014.mdb -

Then found the fresh blank copy of the JCapper.2.mdb file in (filename: c:\JCapperBuild\JCapper2.mdb) and copied the file to my c:\JCapper\Exe folder.

From there I used the JCapper2 Import Module to import the sql factor setup and html report layout out of your old file into your new file -

Prior to all this, I populated the starter history table for my YTD 2014 folder (I only use playlist and not sql) using the data window export using the Starter History Clear First option. Once completed I ran a Compact and Repair on my jcapper2.mdb prior to renaming it..

Everything looked fine afterwards... I was able to connect to my new 2015 q1 file, download files from the HDW site, use scratch bot, Run a calc race for the race cards I downloaded for 1/1/15... Once my race day was over yesterday, I downloaded the charts from HDW and ran a Build Database using option 3 for the first time...

Then I went into the UDM wizard tweek a few UDM's... Thats when I got an Error message that said:
ERROR: -2147217887 Description - The changes you requested were not successful because they would create duplicate values in the index, primary key, or relationship. Change the data in the field or fields that contain duplicate data, remove the index, or redefine the index to permit duplicate entries and try again. Hit the ok button and got the next message:

UDM XML may not have been logged to the jcapper2.mdb
UDMXML history table. It is recommended that you display (and check) the UDMXML sitting on the Recovery Screen. Hit the ok button, clicked to exit out of the UDM Wizard and received the same 2 messages above...

I am new to all this and don't know what to do to be able to tweek my udms via the UDM Wizard...

Can you help?

Thanks
Jimmy

Reply
Caveat
1/2/2015
12:55:35 PM
OK..

Before I mess things up om my first build of new data base..

I rename my jacapper2 file to jcapper2_old

Then I copied a new jcapper2 from build to exe folders..

All is good..

Now its time to IMPORT...

There are 18 boxes to check off
and
A "Set Source" and
A "Set Target"

Do I check all boxes and use jcapper2_old as "Set Source"
and use jcapper2 as "Set target"

thxs

Reply
Caveat
1/2/2015
3:17:27 PM

Just received numerous errors like in the guys post above mine...


I started over with a clean jcapper2 file and the import went fine..

~Edited by: Caveat  on:  1/2/2015  at:  3:17:27 PM~

Reply
SILVER01HDW
1/2/2015
3:37:54 PM
There are 18 boxes to check off
and
A "Set Source" and
A "Set Target"

Do I check all boxes and use jcapper2_old as "Set Source"
and use jcapper2 as "Set target"
---------------------------------------------------------------------

How did you handle the import part? Did you check "All Boxes" during the import the 2nd time around or something else?

jm

Reply
Caveat
1/2/2015
3:41:39 PM

I checked the "all of above"
left append open

~Edited by: Caveat  on:  1/2/2015  at:  3:41:39 PM~

Reply
jeff
1/2/2015
4:49:39 PM

--quote:
"From there I used the JCapper2 Import Module to import the sql factor setup and html report layout out of your old file into your new file..."
--end quote


and


--quote:
"Then I went into the UDM wizard tweek a few UDM's... Thats when I got an Error message that said:
ERROR: -2147217887 Description - The changes you requested were not successful because they would create duplicate values in the index, primary key, or relationship. Change the data in the field or fields that contain duplicate data, remove the index, or redefine the index to permit duplicate entries and try again. Hit the ok button and got the next message:

UDM XML may not have been logged to the jcapper2.mdb
UDMXML history table. It is recommended that you display (and check) the UDMXML sitting on the Recovery Screen. Hit the ok button, clicked to exit out of the UDM Wizard and received the same 2 messages above..."
--end quote




my reply:

My Bad.

Instead of: "import the sql factor setup and html report layout out of your old file into your new file"

Try it the way I did it in this screenshot:
www.JCapper.com/Messageboard/Avatars/JCapper2_Import_01022015.jpg



-jp


.


Reply
SILVER01HDW
1/2/2015
10:57:05 PM
Still getting the same messages... But I just noticed in your screen shot you do not have the starter history table checked... Is that correct? I think when I re-ran my import, I had it checked...

Thanks
jm

~Edited by: SILVER01HDW  on:  1/2/2015  at:  10:57:05 PM~

Reply
jeff
1/3/2015
12:20:46 AM
That is correct. -- Although as long as the UDM Wizard XML Recovery Screen box is checked when you run the Import it shouldn't make a difference (meaning you shouldn't be getting an error message when you go to update a UDM.)

Tell you what...

If you'll do the following:

Use a free large file transfer service such as WeTransfer.com to send the following files to jeff @ jcapper . com -- hint: remove the blank spaces first:

a. Your old (source) JCapper2.mdb file.

b. Your c:\2004\JCapper.mdb file (that's the file that contains your UDMs.)

c. The name of the offending UDM that you tried to update.

I'll be happy to:

a. Run the J2 Import at my end.

b. Test to see that you can update UDMs using the UDM Wizard.

c. Send you back a working JCapper2.mdb file and c:\2004\JCapper.mdb file.

-jp

.

Reply
SILVER01HDW
1/3/2015
1:47:09 AM
Thanks Jeff... Just sent it to you...

Reply
Caveat
1/3/2015
8:53:59 AM

All went well using the 6 boxes checked

thxs

Reply
Reply

Copyright 2018 JCapper Software              back to the JCapper Message Board              www.JCapper.com