Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC Microsoft Access Driver] Operation must use an updatable query
If you received this error while accessing your database you need to contact us so that we can change permissions on the directories for you. Contact us through our ticket manager.
Back to top
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC Microsoft Access Driver] Cannot open database '(unknown)'. It may
not be a database that your application recognizes, or the file may be corrupt.
Since we are using the latest MDAC, it is not compatible with Access 97 databases. You may find that your database worked originally, however once you write data to the database it will throw this error. If this is an Access 2000 database it is likely that is it corrupted. Should you be using an Access 97 database please convert it to the 2000 version via Access 2000 or later.
Back to top
I would like to upload an updated version of my access database. When I atttempt to overwrite the existing database I am unable to.
As a normal part of ODBC operation, your database file is locked by the ODBC connection. There is a trick you can use to unlock the database temporarily. You can write a page to query a non-existent column in an existing table in your database. This will temporarily unlock the database so that you can overwrite the file. Since the file will be re-locked quickly, especially if other pages are accessing the database, it is best to rename or delete the old database before uploading the new one. As soon as you upload the new database and run a good query, normal ODBC operation will resume.
There are a few things you can do to maximize the success of the unlock page:
- Make sure that no other pages are executing queries on the database. If a valid query is run right after your invalid query, the database will be locked again.
- Since the database can be re-locked quickly, rename the .mdb file as soon as you run the invalid query. Then you can upload the new database and not worry about it locking again before you have a chance.
- This trick often requires some patience - if it doesn't work at first, try it again a few times. Also, you may want to wait a few minutes and then try. You may want to rename, disable, or move any pages that query the database to prevent them from re-locking it.
- If all else fails, upload another copy of the database with a different name. contact Flarehosting.com through our ticket manager and we will adjust the DSN.
Back to top
SQL Server registration or Enterprise Manager Timing Out.
- Customers must upgrade Microsoft SQL 2000 installed on their local computer to Service Pack 3. Download Link
- Make sure you have the latest MDAC from microsoft. Download Link
- Change the timeout value in Enterprise Manager's "Tools -> Options " Menu to 0.
*Also Note, previous versions of Enterprise Manager will not work. Enterprise Manager 2000 is required.
Back to top
| |
|
|
