|
JCapper Message Board JCapper 101
|
| Home |
Register
Log In |
| By | Problems with SQL reports and data queries | |
| joe v 9/4/2010 8:49:44 PM | I am able to run data queries and reports in playlist file mode, but when attempting to use SQL mode I cannot change factors on the HTML report and strangely enough, cannot run data reports which display any results beyond Aug 12, even though I update both files on download and use the appropriate settings for display. If anyone has experienced similar problems please give me some help......I can't keep bugging Jeff over this problem. Joe V
| |
| jeff 9/4/2010 10:23:08 PM | --quote: I am able to run data queries and reports in playlist file mode, but when attempting to use SQL mode I cannot change factors on the HTML report and strangely enough, cannot run data reports which display any results beyond Aug 12, even though I update both files on download and use the appropriate settings for display. If anyone has experienced similar problems please give me some help......I can't keep bugging Jeff over this problem. Joe V --end quote-- Actually, you CAN bug Jeff over this problem.  Try this: 1. Run a Compact and Repair of the JCapper2.mdb file. In the Data Window, click MENU. Then select Compact and Repair JCapper2.mdb File. Use the dialog box that pops up to select your c:\JCapper\Exe\JCapper2.mdb file and run the compact and repair routine by clicking the Open button. 2. Use the Data Window to Clear and repopulate the StarterHistory Table: a. Put the Data Window in Playlist File Mode. b. Point the Data Window at your first target folder. c. Click MENU. Then select Exports. Then select StarterHistory Table Next Query Clear First. Answer Yes at the prompts to toggle the Export "On." d. Run an ALL Button query of the pl_profile.txt file of your target folder. As part of running the query, the Data Window will clear the starterhistory table and then write all of the data returned by the query to the starterhistory table. e. Point the Data Window at your next target folder (provided that you have more than one.) When you are out of target folders, goto step i below. f. Click MENU. Then select Exports. Then select StarterHistory Table Next Query Append. Answer Yes at the prompts to toggle the Export "On." g. Run an ALL Button query of the pl_profile.txt file of your next target folder. As part of running the query, the Data Window will simply append all of the data returned by the query to the starterhistory table while leaving existing data in the table intact. h. Move on to the next target folder and repeat steps f and g until you are out of target folders. i. When you are out of target folders, run a final compact and repair. At this point, your table should be repopulated and all should be well. If this is not the case, CALL ME on my cell phone. 8 5 8 - 8 6 9 - 7 2 6 9 -jp . ~Edited by: jeff on: 9/4/2010 at: 10:23:08 PM~
| |
| jeff 9/4/2010 10:26:07 PM | --quote: "I cannot change factors on the HTML report...--end quote Joe, The phrase "cannot change factors on my html report" covers a lot of ground. Give me a call sometime tomorrow on my cell phone. I'm more than happy to talk you through it. -jp .
| |
| joe v 9/5/2010 9:45:18 PM | Jeff, Thanks, your suggestion cleared up the problem, but now that I have the ability to do the data work I have a question. How would I structure a query to bring back results for an odds requirement to be applied to both separate ranks of a single factor, not an either or situation? Thanks again. Joe
| |
| jeff 9/6/2010 3:27:38 PM | --quote: "How would I structure a query to bring back results for an odds requirement to be applied to both separate ranks of a single factor, not an either or situation?"--end quote If you have something like the following and you are looking to build in odds constraints for each of the two rank conditions... AND (RANKJPR = 1 OR RANKJPR = 2) My recommendation would be to use separate UDMs. IMPORTANT: Be aware that when you click the Calc Races button on race day, the odds are not known by the Profile Marker. It is programmed to evaluate the odds as if they were equal to zero. The Data Window, on the other hand, DOES have access to odds based information. For that reason, odds constraints, and handles to odds based factors will work in the Data Window but not in the Profile Marker. Use the Data Window to perform R&D and determine what cutoffs you want to use on race day. Use the BettingInstructions Field in the UDM Wizard to write yourself a note to remind you what cutoffs you are looking for on race day. Something simple like "4-1 up" (without the quotes) will serve to remind you that you want 4-1 or higher on race day before betting the selections of an individual UDM. Use the BettingInstructions Field instead of building the odds constraint into the sql expression of the UDM. -jp .
|
| Reply |
|
Copyright © 2018 JCapper Software back to the JCapper Message Board www.JCapper.com |