|
JCapper Message Board
JCapper 101
--
Wager History Short Description
|
|
By |
Wager History Short Description |
NYMike 2/13/2022 4:52:28 AM | When I try to delete a Short Description in Wager History, it does not delete. It seems to create a blank space in the drop down list but not l delete the one selected.
Any suggestions?
Mike
~Edited by: NYMike on: 2/13/2022 at: 4:52:28 AM~
| jeff 2/17/2022 6:22:39 PM | Definitely working as designed at my end.
Here's what I did:
1. I brought up the WagerHistory Module by clicking the WgrHist button on the face of the Main Module.
2. On the WagerHistory Module I clicked the Short Descr Setup button.
3. On the Short Descr Setup screen I clicked the New button, keyed the letters "_Test" (without the quotes) into the Short Description box, keyed "This is only a test" (without the quotes) into the Long Description box, and hit the Save button.
Screenshot here:
From there the Interface created the new Short Description, and I verified that the Short Descr code "_Test" (without the quotes) was visible in the drop down.
4. On the Short Descr Setup Screen I selected the Short Descr code "_Test" (created in step 3 above) from the drop down, hit the Delete button, and answered Y at the prompt.
Screenshot here:
5. After that, I opened up the drop down - and can clearly see that the "_Test" Short Description is no longer displayed - and has therefore been deleted.
Screenshot here:
If you're getting behavior other than this my first best guess at a solution might be to try the following:
1. Close down the WagerHistory Module.
2. Run a compact and repair on the c:\JCapper\Exe\JCapper2.mdb file.
3. Relaunch the the WagerHistory Module and give it another go.
As to root cause(s) for behavior other than what I typed above, my first best guess would be:
1. Some other app (the Data Window, the JCapper Main Module, the JCX File Exports Module, or a third party database app, etc.) has an active connection to and has established an .ldb lock file on the c:\JCapper\Exe\JCapper2.mdb file. (This would prevent the WagerHistory Module from connecting to and altering table content in the c:\JCapper\Exe\JCapper2.mdb file.)
2. It's also possible that the c:\JCapper\Exe\JCapper2.mdb file has become corrupt because it broke the 2.0 gigabyte file size barrier.
As a test: You could try a file rename of your current c:\JCapper\Exe\JCapper2.mdb file to something like c:\JCapper\Exe\JCapper2_SavedForNow.mdb to get the file out of the way for testing purposes - followed by putting a copy of the fresh blank JCapper2.mdb file from your c:\JCapperBuild folder onto your c:\JCapper\Exe\ folder.
After that try repeating the Wager History Module steps that I posted above.
If you are able to add and delete Short Descr's at will like I am able to do at my end: That's a pretty good indicator that your current c:\JCapper\Exe\JCapper2.mdb file has become corrupt (possibly because it broke the 2.0 gigabyte file size barrier.)
-jp
.
|
|