I'm getting an "Unspecified error: E_FAIL(0x80004005) when creating an Access based project. The connection is OK, and I've created other Access based projects in the past.

Here is the stack trace: -----[Core exception]-------------------- at System.Data.OleDb.OleDbConnection.ProcessResults(Int32 hr) at System.Data.OleDb.OleDbConnection.GetSchemaRowset(Guid schema, Object[] restrictions) at System.Data.OleDb.OleDbConnection.GetOleDbSchemaTable(Guid schema, Object[] restrictions) at SD.LLBLGen.Pro.DBDrivers.Access.AccessCatalogRetriever.RetrieveSchemas(String connectionString, IDBCatalog catalogToRetrieve, SchemaFetchFlags fetchFlags) at SD.LLBLGen.Pro.DBDrivers.Access.AccessDBDriver.PopulateSelectedCatalogs(Hashtable callBacks, Hashtable connectionElements, SchemaFetchFlags fetchFlags, Hashtable properties) at SD.LLBLGen.Pro.Gui.Forms.NewProjectWizard.CreateNewProject()

Any ideas? Thanks, Bill

It's not marked read-only is it?

No, the file attribute itself is RW (not Read-Only). Additionally, its located in a local folder with RW privledges.

CvilleBill wrote:

No, the file attribute itself is RW (not Read-Only). Additionally, its located in a local folder with RW privledges.

Strange... it seems data is returned which crashes the OleDb driver for Access. This could be something with MDAC (ado objects, ole db drivers in windows). The activities taking place are unique constraint retrieval and foreign key retrieval.

Your access mdb file is of a format of access 2000 and you don't use linked tables in it? (linked tables with sqlserver 2000 for example)

Ah ha! Linked tables... I removed those from my DB and was able to create the project. I guess linked tables are a no no (even though they linked back to another Access database.) Assuming you can detect linked tables, might want to throw a better message up.

OK, I can work around that by copying the table structure over for the gen phase. Any clue if linked tables will work from the generated code?

Thanks, Bill

CvilleBill wrote:

Ah ha! Linked tables... I removed those from my DB and was able to create the project. I guess linked tables are a no no (even though they linked back to another Access database.) Assuming you can detect linked tables, might want to throw a better message up.

It's the Access OleDb driver which crashes (JET engine), so unfortunately I can't do much about it.

Investigating what I get back from GetOleDbSchemaTable, I see that 'LINK' is the table type for a link table. Though, I can't specify a filter for GetOleDbSchemaTable to EXCLUDE tables for a given operation (like getting the FK information/uc information). So that whole operation has to be skipped because the access JET engine otherwise crashes... I'm not sure that's a good idea.

OK, I can work around that by copying the table structure over for the gen phase. Any clue if linked tables will work from the generated code? Thanks, Bill

If the Access JET engine is up to it, it should work. If it fails, it's up to the JET engine why it fails, all LLBLGen pro does is executing queries on the access db it's connected to.