|
JCapper Message Board JCapper 101
|
| Home |
Register
Log In |
| By | Finding name and race ID after a query | |
| Windoor 7/12/2012 4:34:21 PM | Does J/Capper output the race ID number and horse name after a query? Maybe somewhere I can see and copy from Access? I can see the information if I click on "show individual plays", but I need to be able to quickly copy the information in the below format for two columns in my Excel sheet. Column G ----------------Column H Horse Name ---------- ---- RACE ID TIMELESS FACTS ------ 20120712APX01 I'm talking thousands of races, so doing it by hand is not an option. It must be a copy and paste operation. I would like to be able to rename a group of horses that have passed some J/Capper filters, then move the qualifiers back into Excel for further study and to help with daily play operations. I can do it now from Excel to J/Capper, but not from J/Capper to Excel. Regards, Windoor.
| |
| jeff 7/13/2012 1:12:35 PM | You could use the JCX File Exports Module to export the contents of a StarterHistory Table to a .csv file. First, a cut and paste from an earlier post about the JCX File Exports Module: JCX File Exports Module This new module is designed for players who want to work with JCapper data outside of JCapper. Screenshot -click here- The module provides a simple interface designed to facilitate generation of .txt and .csv export files. Basic Operating Instructions: • Close all open JCapper program windows except the JCapper Main Module. Also close all open program windows where the app open in the window (Excel, Access, 3rd party db app, etc.) has a current lock file placed on the file name for the export file you are about to generate. • To launch, on the face of the JCapper Main Module, click System Settings. Then click JCX File Exports. • Check a source table. Options are StartersToday and StarterHistory. • Select an Action. Valid options are Create New File and Append to Existing File. • Select a File Extension. Valid options are .CSV (the default option) and .TXT (the alternate option.) • Click the Browse button and supply a file name for your export file. Use the dialog box that appears when you hit the Browse button. The very first time you do this for a given folder you will need to manually key a file name into the file name field of the dialog box. Each subsequent time that you generate an export file for the same folder you can supply the file name by selecting an existing file appearing in the dialog box. Note that the dialog box will auto point at the current active data folder as set in the DFM. Also note that a DFM launch button has been provided in the event that you want to point the module at a different folder. • Click the Create Export File button to generate your export file. • Import the export file into Excel or the 3rd party app of your choice. Requirements for making it work: Export files generated by this module contain data if and only if the selected source table is populated with data. Note that the default StartersToday table is populated with data when you run a Calc Races in SQL Mode. Also note that this table is overwritten each time that a SQL Calc Races is run. Note that the (larger) StarterHistory table is populated with data whenever you run a Build Database routine in modes 3, 4, or 5. If your source table has not been pre-populated with data, export files generated by this module will be empty. File format and field mapping: Export files generated with this module are simple comma delimited text. Except for the top row, file content is an exact replication of data sitting in the selected source table. Data fields in the top row of each export file are populated with the field names as read from the selected source table. This makes it easy to know what data is in each column. To test: Run a sql calc races, select the StartersToday table, create a new export file, and import the export file into Excel. The actual field names from the StartersToday table will appear as the column headers for the top row when Excel renders the export file. Where to find export files: Export files generated by this module are written to the current active data folder checked in the DFM. More to come... -jp .
| |
| jeff 7/13/2012 1:32:51 PM | Before running the export, the content of the data sitting in the starterhistory table can be driven by Data Window Export. For example, if you wanted the starterhistory table to contain only those starters flagged by a handful of UDMs, do the following: 1. Rename your current c:\JCapper\Exe\JCapper2.mdb file to preserve it - prevent it from being overwritten by the Data Window Export procedure presented below. Renaming it from c:\JCapper\Exe\JCapper2.mdb to c:\JCapper\Exe\JCapper2_07132012.mdb will get the job done for this purpose. 2. Copy the fresh blank copy of the c:\JCapperBuild\JCapper2.mdb file from the c:\JCapperBuild folder to the c:\JCapper\Exe folder. IMPORTANT: Make sure you rename the file in step 1 above first! Otherwise you run the risk of overwriting your current file. 3. Use the JCapper2 Imports Screen (the one in the WagerHistory Module is the most current) to import your SQL Factor Setup from your saved JCapper2.mdb file (from step 1 above) into your new JCapper2.mdb file (from step 2 above.) At this point, you have a JCapper2.mdb file sitting on the c:\JCapper\Exe folder that is ready to accept new data. 4. Use the Data Window (and its Data Window Export capability) to populate the starterhistory table in the JCapper2.mdb file created in step 2 above and made ready in step 3 above. Link to a thread where you'll find instructions for populating a starterhistory table using Data Window Export: http://www.jcapper.com/messageboard/TopicReader.asp?topic=1044&forum=JCapper%20101 After populating the starterhistory table in the c:\JCapper\exe\JCapper2.mdb file, you can now do the following: A. Use the JCX Exports Module to export data from the starterhistory table to a .csv file - where it can then be imported into Excel (where you can manipulate the data to your heart's content.) B. Rename your JCapper2.mdb files: c:\JCapper\exe\JCapper2.mdb becomes (for example) c:\JCapper\exe\JCapper2_ExportedToExcel_07132012.mdb and c:\JCapper\exe\JCapper2_07132012.md from step 1 above becomes c:\JCapper\Exe\JCapper2.mdb so that it becomes your current file once again so far as the JCapper program is concerned. Hope I explained most of that in a way that makes sense. -jp . ~Edited by: jeff on: 7/13/2012 at: 1:32:51 PM~
| |
| Windoor 7/13/2012 6:51:53 PM | Jeff, Thank-you. This looks like it will work, but will take some time to get my head around it. I'll give it a go after I have some coffee and a couple of hours to work on it. I may need some help with my latest database build for the 1st quarter of this year. I keep getting an error message "55 at main module command 19_click() view exception report already open" "269 cards processed" I have 1038 in the folder. I am in the process of installing the latest program update and running a compact and repair database routine before trying again. I'm hoping this will fix the problem. If not, I'll need some assistance. Regards, Windoor.
| |
| Windoor 7/13/2012 7:18:43 PM | If it is not one thing it's another. After installing the latest update and running a compact and repair routine. The database builds stops at 269 and crashes the program as above. These are modified files, but I have done this many times before without a problem. Maybe a corrupt file? Regards, Windoor
| |
| Windoor 7/14/2012 7:58:32 AM | Update: Maybe I should start a new thread instead of hijacking this one. I pulled just one track from this folder and all went well when building the database. So, I'm thinking one or more of the files are corrupted and crashes the build? Is there anyway to check them to see which ones? Regards, Windoor
| |
| jeff 7/14/2012 10:59:23 AM | Before I ask you to spend a bunch of time debugging your build - STOP! You're running JCapper Silver, right? On July 8th I published a JCapper Platinum new program update - that among other things - addressed the db build issue you are reporting. Here's a link to the .pdf release notes for that new program update: http://www.jcapper.com/helpDocs/newprogramupdate_07082012.pdf The release notes about the updated Main Module contain a description about the bug. It's been an incredibly busy week for me - and I have yet to publish a Silver program update addressing this. (I'll do what I can to make that happen sometime this weekend.) If you can wait until then, chances are you can run the build to completion (without the error.) If that turns out not to be the case - and something else is causing the problem - and if you have a high speed internet connection - I can get you an ftp account so that you can upload the entire folder to a server at JCapper.com. From there, I'll be able to run a build database routine using the program's dev environment - and if I can replicate the same error - I'll be able to see exactly what the problem is - and go from there. Alternately - for those of you interested in how to identify specific files causing a build to fail... General Info - Debugging Failed Build Database Routines The info for each build can be found in a series of text files on the folder being built. The filenames start with the characters "DO_" (without the quotes) and end with the characters ".txt" (again without the quotes.) Characters bearing the date of the build appear in the filename immediately to the right of the underline character. Because these are text files, double clicking them causes them to pop open in Notepad - where the content becomes readable to the human eye. DO_1 .txt files are normally empty when a build database routine runs to completion without error. Each DO_2 .txt file contains the .DAT file names of the race cards that make up the current build database routine. The DO_3.txt file contains the .DAT file names - which in turn provides the track code, month, and day of month for each race card that was made part of both the current build as well as all previous builds on the folder. The .DAT file names in the DO_3 .txt file appear in the order they were made part of a build database routine. A look inside the DO_3.txt file will tell you at a glance where the build stopped. -- Depending on what interrupted the build, sometimes the last file shown in the DO3_.txt file is the problem file. Sometimes it's the second to last one listed. And sometimes it's the next logical file yet to be built - but because of when the build was interrupted, has not yet been written to the DO_3.txt file. -jp . ~Edited by: jeff on: 7/14/2012 at: 10:59:23 AM~
| |
| Windoor 7/14/2012 2:09:23 PM | Jeff, Thank you for the reply. Yes I am still using the Silver. As I have never experienced any type of problem when building databases. ( I have many and more) I just "assumed" the problem was with my modified data. I did something a little different this time, but still just changing the names in some fields so it points to qualifying horses. I have Zero problem with waiting for a fix, assuming (there's that word again) the problem is with the software. The earliest I would use any of the research I am doing now would be the fourth quarter of this year. Some very interesting things can show up when you can look at 75K consecutive races. In the mean time I will delete the last two and next file of the build as listed in the DO_3.txt file, just to see if that fixes it. I do have a fast internet connection, so uploading should not be a problem. If you are just a little curious as to what I have been doing with modified files, run a couple of your favorite udm's with the owner's name listed as "SPOTG10" (without the quotes) you might be pleasantly surprised. Regards, Windoor
| |
| Windoor 7/14/2012 3:17:01 PM | Update: I deleted the last two cards and the next in line as above and now the database build completed successfully. As long as know a work around, I'm happy. I did notice one of the files was very small, even for an .XRD, so maybe that one was causing the problem. Regards, Windoor
| |
| jeff 7/15/2012 10:36:51 AM | Since you know the specific filenames - can you take them off your recycle bin and send them to me? -jp .
| |
| Windoor 7/15/2012 10:53:20 AM | Sure, coming at you. I think I will have to send four cards in all, but I am sure one of them was causing the problem Regards, Windoor
|
| Reply |
|
Copyright © 2018 JCapper Software back to the JCapper Message Board www.JCapper.com |