Bubi

Ok, I had a look to the first pdf. You can do the same thing updating the source code and using the BuildTablesFromPdf.Renderer app. The table in the first page...

Could you send me the code? THX!!!

As far as I remember we can't avoid to use OleDb because we risk to loose code from DB features. Microsoft Access does not have (sorry, has few) system tables...

@lauxjpn I updated the comment sorry. I think that with ODBC we can't retrieve the tables list.

@lauxjpn there is a small issue about `MSysObjects` and `MSysRelationship`. The user does not have enough rights to select from it. Just to remember a solution I copied this workaround...

I think we should do a proof of concept. There are several issues related to, for example, OleDb and union queries (you can find quite "strange" code in System.Data.Jet.DataReader about...

About **AccessViolationException** did you try to run tests **disabling connection pooling**? I've implemented a connection pooling inside System.Data.Jet because I had some issues with OleDb connection pooling. We could check...

> > About AccessViolationException did you try to run tests disabling connection pooling? > > Yes, its one of the first things I checked, because of my previous post on...

About Jet/ACE provider for OleDb, there is an issue related to the wrong data type determined in union queries when you use const values, for example ``` SELECT null FROM...

> The other way would be for `System.Data.Jet` to not have a default data access library defined, and make it mandatory for the user to specify, which one to use...