Consider the following SQLs:
Select firstname, lastname from employee Select firstname, lastname from myschema.employee
This basic example creates an ambiguity:
By default, the Visual Expert code parsers cannot know whether employee and myschema.employee refer to the same table. Unless we remove this ambiguity, Visual Expert will duplicate the table employee.
To avoid similar issues in your code, you need to specify a schema, database and server, that Visual Expert will apply by default when they are not explicitly indicated with a prefix before the Oracle object.
In the example above, if myschema is specified as default schema, then the Visual Expert code parser will automatically identify the table employee as myschema.employee, and the table employee will not be duplicated in the VE project.
First, find the name of the database and schema containing the duplicated objects.
Then, use these value as default database and schema in your VE project.
a. Open a list of objects in Visual Expert and select some duplicated objects.
b. Click “Locate” in the navigation bar : the database and schema containing the objects are displayed.
c. note down the server, database and schema names.
Once the analysis process is completed, check that the objects are no longer duplicated.
Eventually, you will see both PowerBuilder and Oracle objects in the treeview: