Causes of Urecognized Database Format
-
Hi all, Every time my code tries to connect to my 2007 Access database, the message Unrecognized Database Format pops up. I've read that it is usually due to a corrupt database file or opening an old Access database file in newer version of Access Database. I can rule out opening an old file in newer Access because I've created and run the file in Access 2007. I can reasonably assume that since I can open the file, it is not corrupt. If those two aren't the causes what else could be causing it? The connection string in my web.config file takes the following form: Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\myFolder\myAccess2007file.accdb;Persist Security Info=False; I don't know if that has anything to do with it, any suggestion will be greatly appreciated, thanks for your time.
-
Hi all, Every time my code tries to connect to my 2007 Access database, the message Unrecognized Database Format pops up. I've read that it is usually due to a corrupt database file or opening an old Access database file in newer version of Access Database. I can rule out opening an old file in newer Access because I've created and run the file in Access 2007. I can reasonably assume that since I can open the file, it is not corrupt. If those two aren't the causes what else could be causing it? The connection string in my web.config file takes the following form: Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\myFolder\myAccess2007file.accdb;Persist Security Info=False; I don't know if that has anything to do with it, any suggestion will be greatly appreciated, thanks for your time.
This information is REALLY old, there used to be an option to compile and compress an Access database. If this option is still available I suggest you use that. Being able to open the database does not mean it is not corrupted.
Never underestimate the power of human stupidity RAH
-
Hi all, Every time my code tries to connect to my 2007 Access database, the message Unrecognized Database Format pops up. I've read that it is usually due to a corrupt database file or opening an old Access database file in newer version of Access Database. I can rule out opening an old file in newer Access because I've created and run the file in Access 2007. I can reasonably assume that since I can open the file, it is not corrupt. If those two aren't the causes what else could be causing it? The connection string in my web.config file takes the following form: Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\myFolder\myAccess2007file.accdb;Persist Security Info=False; I don't know if that has anything to do with it, any suggestion will be greatly appreciated, thanks for your time.
ASPnoob wrote:
I can reasonably assume that since I can open the file, it is not corrupt.
Wrong assumption. The database is corrupt; usually when Access terminates within a write - it can not ammend the database with random bites when it comes back online, so, you get the next best thing; you get to see the database, as Access thinks that the underlaying data should be. So, install Sql Server Express and start upsizing all the tables that are still within the database, and have the Wizard migrate the data with it. Did your database allow access to multiple users simultaneous?
Bastard Programmer from Hell :suss: if you can't read my code, try converting it here[^]
-
ASPnoob wrote:
I can reasonably assume that since I can open the file, it is not corrupt.
Wrong assumption. The database is corrupt; usually when Access terminates within a write - it can not ammend the database with random bites when it comes back online, so, you get the next best thing; you get to see the database, as Access thinks that the underlaying data should be. So, install Sql Server Express and start upsizing all the tables that are still within the database, and have the Wizard migrate the data with it. Did your database allow access to multiple users simultaneous?
Bastard Programmer from Hell :suss: if you can't read my code, try converting it here[^]
Thank you, everyone for responding. My database was created less than 10 minutes prior to testing it in my code. It only has one table with one field in the table. I just cannot understand how it could be corrupted. I will give everyone's suggestion a try, thanks again for your reply.
-
Thank you, everyone for responding. My database was created less than 10 minutes prior to testing it in my code. It only has one table with one field in the table. I just cannot understand how it could be corrupted. I will give everyone's suggestion a try, thanks again for your reply.
Did you use Microsoft Access in an environment where multiple users would manipulate data at the same time? Is your database on some network-share? Microsoft Access is a damn good tool to manipulate single-user local-file databases with strong reporting capabilities. It's not built to be a sharing-facility for data. If that's what you need, you'll need to switch to a real server - otherwise crap like this will happen again.
Bastard Programmer from Hell :suss: if you can't read my code, try converting it here[^]