Re: Transparent database objects after merging

[Arup Nanda]

You can drop or rename CUSTOMERS to, say, CUSTOMERS_A, and then create synonym CUSTOMERS pointing to CUSTOMERS_B. Or rename CUSTOMERS_B to CUSTOMERS.   HTH.   Arup Nanda ----- Original Message ----- From: [EMAIL PROTECTED] To: Multiple recipients of list ORACLE-L Sent: Tuesday, July 15, 2003 11:29 PM Subject: Transparent database objects after merging Hello Gurus,         I'm working merging 2 databases which have sane structure of  database objects into one database. However, after merging, the business policies and regulations force us to have 2 set of database objects; for example : Database A has CUSTOMERS table. Database B has CUSTOMERS table. After merging database A will have CUSTOMERS and CUSTOMERS_B (data from database B). I just wonder that is there any way that we don't need to change our script in forms and reports to point into a new table name but still can access to the data in the new table ( CUSTOMERS_B) not CUSTOMERS. Thank you for any comment and suggestion. Ukrit K,