|| windows xp
|Jcapper no longer opens on windows xp|
--error -- 'Cannot open the microsoft jet engine workgroup
Does this mean jcapper will not run on xp anymore ??
|Not at all. (It most likely means Windows failed to clear an .ldb "lock" file for one of the two .mdb database files... either c:\2004\JCapper.mdb or c:\JCapper\Exe\JCapper2.mdb.)|
I Googled the phrase "vb6 xp Cannot open the microsoft jet engine workgroup information file" (without the quotes) and came up with the following link at dbforums.com where someone had asked the same question you are asking (not JCapper but another app) and someone else had come along and posted a description of the problem along with a working solution:
1. Close all open program windows and restart your machine. This will ensure that all JCapper program windows are closed as well as windows for any other programs (Access, Excel, etc.) capable of placing an .ldb "lock" file on an .mdb file.
1. Launch Windows Explorer - Right Click your Windows Start button and select "Explore" or "Open Windows Explorer" to accomplish this. Alternately you can go into "My Computer" to do the same thing.
2. Navigate to your c:\JCapper\Exe folder and sort the files by Name.
Hint: To see details instead of icons right click inside the folder and select details. Then click the column header labeled Name at the top of the window to sort the files on that folder by Name.
3. Find the JCapper2.mdb file on that folder. Then look for a second JCapper2 file on that folder named JCapper2.ldb.
Hint: If your folders are not setup to display file extensions, hovering a mouse cursor over the file should reveal the file type. The JCapper2.mdb file will be a "Microsoft Access Database file" and the JCapper2.lbd file will be a "Microsoft Access Record Locking Information" file.
4. Delete the JCapper2.ldb file if you have one.
IMPORTANT: Be sure the file that you delete is the .ldb file. Do NOT delete the .MDB file.
5. Repeat steps 2 through 4 for the c:\2004 folder.
Finding a lock file on either folder is the likely root cause behind the problem.
Deleting a lock file found on either folder should solve the problem.
Note: It's entirely possible that performing Step 1 (above) - the act of shutting down whatever program placed a "lock" on the .MDB file in the first place - will cause Windows to delete the offending .ldb "lock" file(s) and solve the problem at that point. If this is the case, you won't find an .ldb "lock" file on either folder, but you should now be able to launch JCapper normally.
Let me know...
~Edited by: jeff on: 4/9/2014 at: 11:49:01 AM~
cannot find a JCapper2.idb file in either folder.
I am now getting a microsoft access message 'unrecognized
--using access 2000
--have never had problem until today !!
~Edited by: Buckabeer on: 4/9/2014 at: 1:04:07 PM~
|Q. What is the size of the c:\JCapper\Exe\JCapper2.mdb file? (Has it grown large enough to have broken the 2.0 gigabyte file size barrier?)|
|--supposedly 678 mb|
|Based on our email exchanges I think you are up and running again. Is that correct?|