DBEngine.CompactDatabase (Access 2K SP3)

Topic

New Reply

My Access program has a line
DBEngine.CompactDatabase……
to compact a database.
The line worked fine in a machine with Access 2000 SP3 and WinXP Pro SP2, but crashed in a machine with Access 2000 SP3 and Windows XP Home SP2. Can anyone give me a clue why it happened this way?

Reply | Quote

Replies

Is the problem consistent, i.e. does it always crash? Have you tried it on other PC’s with Windows XP Home?

Reply | Quote

Is the problem consistent, i.e. does it always crash? Have you tried it on other PC’s with Windows XP Home?

Reply | Quote

Yes, the crash is consistent. I didn’t try it on another Windows XP Home machine as I don’t have one available at the moment. Perhaps I should try. But the “problem” line worked fine in all the WinXP Pro machines as well as Win98 machines that run the Access program.

Reply | Quote

I doubt that Windows XP Home itself is the culprit (although I cannot be sure about this)

Has the latest service pack for Jet 4.0 been installed on the Windows XP Home PC? See How to obtain the latest service pack for the Microsoft Jet 4.0 Database Engine for details.

Reply | Quote

After scratching my head and wasting your precious time in answering my posts, I managed to solve the problem. It wasn’t Windows XP Home nor the version of my MSJet, it was the corrupted back-end data! I actually and simply copied the original data from a WinXP Pro machine to my WinXP Home machine and did some data entry. Then the DBEngine.CompactDatabase surfaced. When I browsed through separately the back-end database with Access, some records had “Invalid bookmark” problem. After replacing the corrupted database with the original one, DBEngine.CompactDatabase works as expected.

Now is my time to find out why the database got corrupted….

Thanks for your reponse, Hans.

Reply | Quote

After scratching my head and wasting your precious time in answering my posts, I managed to solve the problem. It wasn’t Windows XP Home nor the version of my MSJet, it was the corrupted back-end data! I actually and simply copied the original data from a WinXP Pro machine to my WinXP Home machine and did some data entry. Then the DBEngine.CompactDatabase surfaced. When I browsed through separately the back-end database with Access, some records had “Invalid bookmark” problem. After replacing the corrupted database with the original one, DBEngine.CompactDatabase works as expected.

Now is my time to find out why the database got corrupted….

Thanks for your reponse, Hans.

Reply | Quote

I doubt that Windows XP Home itself is the culprit (although I cannot be sure about this)

Has the latest service pack for Jet 4.0 been installed on the Windows XP Home PC? See How to obtain the latest service pack for the Microsoft Jet 4.0 Database Engine for details.

Reply | Quote

Yes, the crash is consistent. I didn’t try it on another Windows XP Home machine as I don’t have one available at the moment. Perhaps I should try. But the “problem” line worked fine in all the WinXP Pro machines as well as Win98 machines that run the Access program.

Reply | Quote