Interesting scenario!

Have you tried setting up two named connection strings in the connection manager?  Not sure how you would trigger this, or if it would work, but when a user needs the data from the other source, simply change the DataSourceKey of the BO to the appropriate named connection.  After that, fill the BO and let the user do his thing.

Not sure if that helps, but at least it keeps the thinking gears rotating.

Bill

Please, respond ASAP. I need to get back to our team to determine what we will need to do to accomodate our Oracle customer in our development process.

We separated the Security Database from the actual Data Database in our application. The Security Database is in SQL Server. We have 2 databases for the Data: one in SQL called VALET_DATA and another in Oracle also called VALET_DATA. Created a Busness Object project called TrustedVALET_BO with a business object mapped to the SQL database table called CUSTOMERS. Created a project called TrustedVALET that has a Customer Maintenance form and dragged the TrustedVALET_BO CUSTOMERS business object to the maintenance form and works perfect for the SQL connection.

Now we need to provide the ability to have a different connection to get the data from the Oracle Database which is called VALET_DATA and the table name is also called CUSTOMERS. The column names in the table CUSTOMERS is exactly the same for both ORACLE and the SQL Data. What is the best way to allow for both SQL and Oracle?

It seems that when the Business Object is created (mapped) it is specific to SQL. Is it possible to use this BO with an Oracle connection? Or do we need to create BOs for Oracle?