Access 2007: Question Regarding Run-Time Error 3049
The error message indicates: "Cannot open database ''. It may not be a database that your application recognizes, or the file may be corrupt."
The database table I am working with totals 352,406 records across 32 fields with a file size of 160,616 KB. The address field (MAILADR3) has combined data (e.g., city, state, and zip code) which is typical in some cases. I would also point out that some records are empty or null, while others are a variety of international addresses. I am parsing the address field into three fields and it is at this point the task has turned into a problem.
My VB code uses the Split function and has been used on others tables ranging to 50,000 records. I am saying this merely to indicate that the code has not perversely been a problem. However, when running this same code on the above larger table it runs fine until it reaches around 162,772 records and halts with the above referenced Run-time Error 3049.
By no means am I saying my code is not the problem, but it seems strange that it ran fine until it reaches a certain point, then stops with an error indicating that it “Cannot open database” or “…the file may be corrupt”.
A little more information: After encountering this error a couple of times I copied (SaveAs) the original database to another name to further challenge the code and data. I was not sure if it was possibly a problem with the data or what was going on. I attempted to visually look at about fifty records above and below where the code stopped, but that was difficult after a couple of minutes. At this point I decided to delete 1,000 records from the top of the table to see if the data was a problem. This was assuming if the data was a problem deleting it may allow the code to continue. Nevertheless, it stopped at 163,131 records. I then delete another 1,000 records from the top of the table, this time it stopped at 163,757 records, and I assume the count difference was related to record size. It is like it reaches a point and stops.
I also used two different machines (Vista Business, Access 2007) repeating the same steps as above with same results. All of these machines are new with 2-3GB Ram and large dives with plenty of free-space, although I am not ruling out a machine problem, but it seems unlikely.
Any ideas…?
The error message indicates: "Cannot open database ''. It may not be a database that your application recognizes, or the file may be corrupt."
The database table I am working with totals 352,406 records across 32 fields with a file size of 160,616 KB. The address field (MAILADR3) has combined data (e.g., city, state, and zip code) which is typical in some cases. I would also point out that some records are empty or null, while others are a variety of international addresses. I am parsing the address field into three fields and it is at this point the task has turned into a problem.
My VB code uses the Split function and has been used on others tables ranging to 50,000 records. I am saying this merely to indicate that the code has not perversely been a problem. However, when running this same code on the above larger table it runs fine until it reaches around 162,772 records and halts with the above referenced Run-time Error 3049.
By no means am I saying my code is not the problem, but it seems strange that it ran fine until it reaches a certain point, then stops with an error indicating that it “Cannot open database” or “…the file may be corrupt”.
A little more information: After encountering this error a couple of times I copied (SaveAs) the original database to another name to further challenge the code and data. I was not sure if it was possibly a problem with the data or what was going on. I attempted to visually look at about fifty records above and below where the code stopped, but that was difficult after a couple of minutes. At this point I decided to delete 1,000 records from the top of the table to see if the data was a problem. This was assuming if the data was a problem deleting it may allow the code to continue. Nevertheless, it stopped at 163,131 records. I then delete another 1,000 records from the top of the table, this time it stopped at 163,757 records, and I assume the count difference was related to record size. It is like it reaches a point and stops.
I also used two different machines (Vista Business, Access 2007) repeating the same steps as above with same results. All of these machines are new with 2-3GB Ram and large dives with plenty of free-space, although I am not ruling out a machine problem, but it seems unlikely.
Any ideas…?
