Replies

Thanks for your lead, Hans. The computer with problem isn’t with me right now. I’ll get back to you after I have tested the Microsoft’s solution.

(Edited by HansV to make URL clickable – see Help 19)

With reference to Access board’s post 209793, I am using VB6 SP6 and the version of my msvbvm60.dll is 6.0.88.42 that comes with Installshield DevStudio SP1’s merge modules.

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.

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.

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.

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.

With a flash of inspiration I chcked the win.ini file and deleted all occurences of “deleted” printer driver, and everything fell into place. My applications now have a default printer driver now. Thanks for your response Wendel.

With a flash of inspiration I chcked the win.ini file and deleted all occurences of “deleted” printer driver, and everything fell into place. My applications now have a default printer driver now. Thanks for your response Wendel.

Thanks HansV for your reminder on TransferDatabase. I have to accept the newly created table into my front-end One of the reasons is I have to rename some of the fields to be used in the legacy application before TrenasferDatabase, and it is easier to do so in the active database.

The main reason I don’t want to touch my front-end is to prevent it from bloating up. I can compact and repair the back-end from my front-end, but I can’t do the same to my front-end without doing it externally.

I checked with the client’s computer with Windows Me, and sure enough the MSJET40.dll was of SP3. I checked my Installshield setup, and discovered that the Microsoft Jet Database Engine 4.0 (which will install version SP6 if the base computer has an older version) was inexplicably left out in the installation package. I include the Microsoft Jet Database Engine 4.0 SP6 again in the installation package, re-install my program, and everything works fine. I am wrong with my earlier assertation that the Jet Database Engine version wasn’t the culprit.

Thanks to HansV and Charlotte for helping me solve the problem.

I checked with the client’s computer with Windows Me, and sure enough the MSJET40.dll was of SP3. I checked my Installshield setup, and discovered that the Microsoft Jet Database Engine 4.0 (which will install version SP6 if the base computer has an older version) was inexplicably left out in the installation package. I include the Microsoft Jet Database Engine 4.0 SP6 again in the installation package, re-install my program, and everything works fine. I am wrong with my earlier assertation that the Jet Database Engine version wasn’t the culprit.

Thanks to HansV and Charlotte for helping me solve the problem.

I know there are incompatiblity problems (though I can’t recall their details) between versions of DAO. My Installshield Windows Installer will install the newer version (BTW, it is version 4.0) in the machine if its DAO is found to be of an earlier version. Surely a Windows Me would have a newer version (?) of DAO than Windows 98, assuming my installer didn’t install DAO 4.0. My program works well with Windows 98. Personally I think version of DAO wasn’t the cause here. Anyway I will check with the DAO version in the Windows Me machine just to satisfy myself that DAO version 4.0 was installed there.

Thanks for your response, Hans.

I know there are incompatiblity problems (though I can’t recall their details) between versions of DAO. My Installshield Windows Installer will install the newer version (BTW, it is version 4.0) in the machine if its DAO is found to be of an earlier version. Surely a Windows Me would have a newer version (?) of DAO than Windows 98, assuming my installer didn’t install DAO 4.0. My program works well with Windows 98. Personally I think version of DAO wasn’t the cause here. Anyway I will check with the DAO version in the Windows Me machine just to satisfy myself that DAO version 4.0 was installed there.

Thanks for your response, Hans.

Thanks HansV. You help me solve my problem. I use the _DblClick event instead of a command button as my list is rather long. Thanks too to Pieterse for responding quickly to my query.

Thanks HansV. You help me solve my problem. I use the _DblClick event instead of a command button as my list is rather long. Thanks too to Pieterse for responding quickly to my query.