-
Omnis 11 and Oracle DAM
Hi there.
I am in the process of updating an Omnis 10 application to Omnis 11.
As part of the connection to the database I have the following line which works in the Omnis 10 code:
Do $root.$extobjects.ORACLE8DAM.$objects.ORACLE8SESS.$newref() Returns lSessionObjRef
However, it appears that the ORACLE8DAM is not included in the list of items in extobjects. I have replaced it with the following line:
Do $root.$extobjects.ORACLEDAM.$objects.ORACLESESS.$newref() Returns lSessionObjRef
The change seems to work.
I have not found anything about the Oracle8dam being deprecated, so I am not sure what is going on. So I have 2 questions:
– Is there something I am missing in Omnis11 to give it access to the Oracle8dam?
– Are there any potential issues with replacing ‘oracle8dam’ with ‘oracledam’? (I haven’t encountered any so far….)
Some details:
– The code was originally maintained in Omnis 10.22.31896 (32 bit)
– The upgrade is to Omnis 11.01.37255 (32 bit)
– The current oracle driver is 32 bit, version 11.2.0.1.0
Thank you in advance
-
1 Reply
-
Hi Allan
The Oracle8 DAM has been renamed to Oracle DAM in Studio 11. (Fault ref ST/*O/201) – the “8” was originally used to differentiate it from the now deprecated Oracle7 DAM.
The DAM and session names ORACLE8DAM and ORACLE8SESS have been renamed to ORACLEDAM and ORACLESESS respectively. In addition, the Oracle DAM object “damora8” is now called “damoracle”. The SQL Browser and VCS have been updated accordingly, as well as the oracledam.ini.
Omnis will map the old name including 8 to the new name without an 8 automatically, for example, when opening the Select Object dialog, and when creating the object.
Log in to reply.
