Hi there
I've got myself into a perculiar proble and I'm suprised it's not more common as it's quite easy to get caught. While running a database the computer rebooted, and did not allow to reopen it, because it claims that me and another user are trying to connect to it. (which is not the case) what is the case though is (in my assumption) that ACCESS wrote something to the file that lets Access know that it is being used and therfore locks it for other users. Since the application did not exit properly, this byte did not get changed back to the original state and therfore it assumes that someone is still connected to it. I'm suppried this doesn't happen more often.
anyhoo - I looked up the JetUtils, but they were not very helpfull as they rely on a .ldb file that the database does not have.
anyone else find a way to go around this ... I've spent way too much time already in hexedit comparing two DB's and don't want to go on like this for much longer.
I've got myself into a perculiar proble and I'm suprised it's not more common as it's quite easy to get caught. While running a database the computer rebooted, and did not allow to reopen it, because it claims that me and another user are trying to connect to it. (which is not the case) what is the case though is (in my assumption) that ACCESS wrote something to the file that lets Access know that it is being used and therfore locks it for other users. Since the application did not exit properly, this byte did not get changed back to the original state and therfore it assumes that someone is still connected to it. I'm suppried this doesn't happen more often.
anyhoo - I looked up the JetUtils, but they were not very helpfull as they rely on a .ldb file that the database does not have.
anyone else find a way to go around this ... I've spent way too much time already in hexedit comparing two DB's and don't want to go on like this for much longer.