After enabling a project to use OpenAccess version Q3 2008 and another project using Q1 2009 the only difference in the app.config file is in the section starting
<section name="openaccess ......". The version Q1 2009 project contains an attribue 'requirePermission="false"' that is not present in the Q3 2008 version. The connection data is the same between the two projects.
Reloading the Q1 2009 version with no reverse engineering mapping does not do anything.
When starting the reverse engineering wizard in the Q3 2008 project the first thing that happens is that an options dialog comes is displayed. In this dialog you select the schema. In the Q1 2009 this options dialog does not appear.
In the Q3 2008 project after saving the configuration from the reverse engineering wizard, the reversemapping.config file ends with an options section that contains a list of all schemata that is contained in the database and a <usedShcemata> tag identifying the schema selected in the options dialog that comes up at the start of the reverse engineering wizard process.
In the Q1 2009 project after saving the the reverse mapping wizard configuration (where there is no prompt to select a schema) there is no list of schemata at the end of the reversmappong.config file, and the <usedSchemata> is set to "(default)". In the database that I am using the default schema has no objects (tables, views etc). If I manually edit the reversemapping.config file so that the <usedSchemata> element points to a valid schema, and then run the reverse engineering schema and do merge changes, I see all the tables in the database and can proceed to finish the wizard and generate the appropriate classes.
It appears that the Q1 2009 version is not able to find the schema in the database.
AN ASIDE: If I am trying to enable a class libary (that does not contain an app.config file) to use openAccess where is the connection information stored?
Having realised that the empty default schema may be the problem, I have tried enabling a project to use OpenAccess Q1 2009 against an oracle database that has objects in the default schema and that works OK!