We use synonyms here. Here's an example of the SQL of a synonym for a view belonging to another schema in a separate tablespace:
-- Create the new synonym create synonym V_MEMBERS for <oracle_user>.V_MEMBERS@<database_link>;
The Pro-IV file def looks like this:
22/06/07 FILE DEFINITION DEV/JPH/PTS_98
CO- AUTO EXTERNAL FILE KEY RECORD DIV SEQUENCED RECORD FORMAT TYPE LENGTH LENGTH FILE NAME: V_MEMBER Y ORA 34 85 ALTERNATE: V_MEMBERS RECORD CODE: MSG: DESC: File definition for V_MEMBERS ODS view Delete -------------------------- R E C O R D L A Y O U T ------------------------- DATA MAX FILL SPECIAL ARRAY SEQ TYPE VARIABLE NAME LEN CODE DISPLAY-CODE CHECK SIZE --- ---- -------------------------------- --- ---- ------------ -------- ----- 001 AK V_MEMBER_DATABASE_NAME 3 002 AK V_MEMBER_EMPLOYER_ACCOUNT_ID 14 003 AK V_MEMBER_EMPLOYEE_DATABASE_NAME 3 004 AK V_MEMBER_EMPLOYEE_ACCOUNT_ID 14 005 A V_MEMBER_MEMBERSHIP_CATEGORY 40 006 A V_MEMBER_EMPLOYER_ACCESS_AUTH 1 007 N V_MEMBER_EMPLOYMENT_CEASE_DATE 10 DATE4 DATE4
I wrote a dummy Pro-IV update function to just select records from this Pro-IV file def and display in the ARNE in a UMSG and got the results as expected.
Not sure what else you need to do Joe. Any other members know something that I have left out?
Jeff.
Click the link below to see the new game I'm developing!