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?

This isn't specific to SQL Server, but rather the database that you pull the schema from.  So if you had mapped to Oracle, then this would have the Oracle data source in there. 

This property is used to create the INSERT and UPDATE commands.  Whether you are using INSERT and UPDATE sprocs or not, this collection gets use to determine how to build the INSERTs and UPDATEs within the DataSourceItem.  So if you have the need to support both SQL and ORACLE on the same BO and receiving an error on updates or inserts when swapping, then you could override this property within your base BO and handle this yourself.

Ah, got it. That makes sense.

Cool