Has anyone seen this error? I copied the file to a different computer and multiple different locations, and it still says another user is in it, which is impossible because of the different location where I copied the file. I also cannot repair it.
Interesting -- try making a copy of the source file and then changing the name of the copy and then try it. the record lock specified in the .lbd file may be against the file name without path instead of the file name that includes the path. If the former, then perhaps gINT thinks it is working on the same file, since the names are the same, and since the first one has the record open, the .ldb file is saying hey you cant do that.
Nope. Didn't work. Also, there no ldb file on the computer that I'm using for this project. That is why it is so weird. Our workaround will be to get a backup from yesterday and then re-enter the data that we entered today. I posted this to see if anyone had any other ideas on how to fix.
do you have ms access on your computer? If so, right click on your .gpj file, and then click Open With and then click Access. Will it open in MS Access? ( The .gpj files are MS Access files)
Same error in access...
These things can sometimes be exhausting but fun ( LOL)( to track down. How about this Compact and Repair??
https://www.stellarinfo.com/article/fix-microsoft-jet-database-engine-stopped-process-error.php#:~:text=What%20Does%20This%20Error%20Means,engine%20exhibits%20such%20a%20behavior.
Yeah - no - tried step 2 didn't work- same error. Can't do Step 3 and 4. Not having fun... Thank you for all your help though! Hopefully this thread might be useful to someone else. I hope this forum doesn't go away when gINT support phases out. It is a great resource! Not ready to go to OpenGround for a few years yet. Too much infrastructure to rebuild.
Uh Oh. Is Open Ground not going to be able to use the gINT files that you are using now???
Hi Monique, it may not be the issue, but I would suggest re-installing your MS Access database engine. I have had a few weird problems that were solved by that, besides the classic "can't open database created with previous version"