DevOps, CI/CD and Automation

Based on what I have read, Justin can certainly tackle this.

We are implementing Office Web Components (active X controls)
that access Oracle 8i DB's. We have a working connection string
within the component but I cannot tell if I am leveraging the MS
driver or native Oracle driver nor tell what type of connection
this is.

The connection string embedded in the MS object has this format:
<x:ConnectionString>Provider=MSDAORA.1;User
ID=myid/mypassword;Data
Source=thisistheservicename_within_tsnnames.ora?
</x:ConnectionString>

Whatever type of connection this is, it appears to need the
Oracle Client because if you attempt connection without Oracle
client installed on the workstation, you receive a MS generated
message indicating you need "Oracle 7.33 or newer client/network
stuff".

In past threads Justin has indicated that the Provider=MSDAORA
line indicates an OLEDB connection??

It seems to me that the connection is a combination of MS and
Oracle. The connection works without a DSN being established
within the ODBC administrator (so does that indicate I am using
an OLEDB connection) What is the difference (in less than 30
words).

Bottom line is that this method works on one machine but not
another with what I believe is the same config. The only
variables relate to the MDAC-MS or Client-ORACLE. If I knew
more about what specific components are being leveraged for the
connection, I think I can isolate the issue.

Any insight would be greatly appreciated.
Thanks for your help!
Greg