jsimpson
Feb 24th, 2000, 11:45 PM
I've written an database archiving utility specific to our application. The database is in access97 format. It basicly copies the active database to an 'archive' location, removes any new records, then connects to the active database and removes any old messages. it then compacts the databases.
It does all this using DAO350.dll. The application works great on NT, but on some 95's & 98's customers have reported the following error: "Can't start your application. The workgroup information file is missing or opened exclusively by another user (Error 3028)"
Microsoft docs suggest that this is caused by an invalid key in the registry as stated here in the MSDN:
"To ensure referential integrity in databases created by the Microsoft Jet database engine, your application must read the Microsoft Jet database's System.mdw file. Make sure the file is in the location specified in the SystemDB value of the \HKEY_LOCAL_MACHINE\ SOFTWARE\ Microsoft\ Office\8.0\ Access\ Jet\3.5\ Engines\Jet key in the Windows Registry."
I've verified this key, have tried to make it invalid (as well as all SYSTEMDB keys in the registry), and can not reproduce this error in my own environment. Yet customers are still saying it is occuring.
Any suggestions???? I am lost.
It does all this using DAO350.dll. The application works great on NT, but on some 95's & 98's customers have reported the following error: "Can't start your application. The workgroup information file is missing or opened exclusively by another user (Error 3028)"
Microsoft docs suggest that this is caused by an invalid key in the registry as stated here in the MSDN:
"To ensure referential integrity in databases created by the Microsoft Jet database engine, your application must read the Microsoft Jet database's System.mdw file. Make sure the file is in the location specified in the SystemDB value of the \HKEY_LOCAL_MACHINE\ SOFTWARE\ Microsoft\ Office\8.0\ Access\ Jet\3.5\ Engines\Jet key in the Windows Registry."
I've verified this key, have tried to make it invalid (as well as all SYSTEMDB keys in the registry), and can not reproduce this error in my own environment. Yet customers are still saying it is occuring.
Any suggestions???? I am lost.