|
JCapper Message Board JCapper 101
|
| Home |
Register
Log In |
| By | Calculate Races error | |
| GlennF 1/3/2010 11:34:58 AM | I am frequently getting the following error when calculating races in SQL mode: Could not update;currently locked.Microsoft JET Database Engine Sometimes I can get rid of the error message by running calculte races over again- sometimes not What causes this error? What can I do to prevent it or workaround it?
| |
| jeff 1/3/2010 12:24:37 PM | Apps like Excel, Access, etc... and JCapper behave in this manner: Before using a db engine (Microsoft Jet) to write to an .mdb file, the app places a "lock" on the file to prevent other applications from writing to the same file at the same time. When the file write is complete the "lock" condition is removed... freeing the file so that other apps can write to it. The most likely cause of the error msg is that the Main Module is attempting to place a "lock" on either the JCapper.mdb or the JCapper2.mdb just prior to running a Calc Races - but is unable to lock the file down because another open JCapper module (the Data Window, the Live Play Module, etc.) already has the file locked. (This would also apply if you have one of the JCapper .mdb files open in a third party app like Access.) Suggestion: Close down or x-out of any open JCapper Modules (the Data Window, the Live Play Module, etc.) or third party apps you are using to read/write to one of the JCapper .mdb files prior to running a Calc Races and the error msg should go away. -jp .
| |
| GlennF 1/3/2010 1:22:52 PM | I am still getting the error message. Usually re running the calc races routine one or more times does the trick but not today. The error message occurs during the export module and races up to the point of the error show on the report. I just discovered that if I calculate the races individually by track they seem to process OK but this does not generate the plays.csv file which I use in an external database. ~Edited by: GlennF on: 1/3/2010 at: 12:55:06 PM~ correction- I get the error message when i do today's SAX individually ~Edited by: GlennF on: 1/3/2010 at: 1:22:52 PM~
| |
| jeff 1/3/2010 1:40:28 PM | Do you have the plays.csv file open in an external database at the time you are running a Calc Races? If so, the external db most likely has a "lock" on the plays.csv file... which would cause the error when JCapper attempts to place a lock on the same file. Try releasing the external db's lock on the plays.csv file first (by closing the external db) prior to running a Calc Races. -jp . ~Edited by: jeff on: 1/3/2010 at: 1:40:28 PM~
| |
| GlennF 1/3/2010 1:29:51 PM | I copy the plays.csv file to my Mac partition and use Mac Filemaker Pro to process it. btw I was able to process files OK before scratches today but the error message appeared after scratches. I was mistaken before and the error message does appear on the SAX file when calculated indivudually (there were no scratches on the SAX file at the time I did scratches.
| |
| jeff 1/3/2010 2:09:02 PM | Glenn, Not having a Mac to test on, replicating the set of circumstances causing the error is likely going to be problematic... but I'm willing to try. I'll set up a new ftp folder on the JCapper server and email you account logon info shortly. If you'll then upload your c:\2004\JCapper.mdb and c:\JCapper\Exe\JCapper2.mdb files, I'll install them on one or more of my own machines, poke around, and see if I can replicate the same error. Not sure where else to go with this... Is anyone else out there getting the same error during a Calc Races? If so, please let me know. -jp .
| |
| TomV 1/3/2010 7:23:27 PM | I get the same error often and by cutting back the # of cards loaded normally get around the error. Typically I can run a max of 4 cards through at a time. Rarely do I try more and every so often I have to cut it down to 1 or 2 cards. Only recall the error happening in SQL mode as the PlayList file mode seems OK. Not sure if its a memory error or a SQL setting that limits the number of records that can be opened or ......... ~Edited by: TomV on: 1/3/2010 at: 7:23:27 PM~
| |
| GlennF 1/3/2010 8:35:35 PM | Tom- It seems I have found a workaround in that if the error appears, if I run the compact and repair routine for the Jcapper.mdb2 file (even though i ran the routine after the last DB update) and recalculate it seems to work OK . I do generally load more than four files so that might have something to do with it.
| |
| nets 1/4/2010 9:46:12 PM | I use SQL mode and encounter this error often when calculating races. Seems the less tracks - the less it occurs. Gary
| |
| ArlJim78 1/4/2010 11:44:14 PM | when I first switched to sql mode I used to run into this error a lot. after talking to Jeff I started to get in the habit of closing all modules before calcuations, plays.csv, data windows, live play mod, etc., and I don't see this error anymore. FYI, I sometimes calc 8-10 tracks at a time with no problem.
|
| Reply |
|
Copyright © 2018 JCapper Software back to the JCapper Message Board www.JCapper.com |