Home » Infrastructure » Windows » Excel 64 bit problem using (19.3)
Excel 64 bit problem using [message #685954] Tue, 10 May 2022 08:53 Go to next message
alcapps
Messages: 7
Registered: May 2022
Junior Member
Set OraSession = CreateObject("OracleInProcServer.XOraSession")
does not work, class not registered. When I try to load the old 32-bit type library that didn't work either.\
Looking for a 64 bit work around.
Re: Excel 64 bit problem using [message #685955 is a reply to message #685954] Tue, 10 May 2022 11:29 Go to previous messageGo to next message
Michel Cadot
Messages: 68216
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

Is your Oracle client a 32 or 64-bit one?

Re: Excel 64 bit problem using [message #685956 is a reply to message #685955] Tue, 10 May 2022 11:40 Go to previous messageGo to next message
Michel Cadot
Messages: 68216
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

Oops! OO4O no more exists in 19c, you have to convert your code using ADODB/OLEDB:
Set OraCon = New ADODB.Connection
OraCon.ConnectionString = "Provider=OraOLEDB.Oracle;Data Source="...;User ID=...;Password=...;"
OraCon.Open
...
Re: Excel 64 bit problem using [message #685957 is a reply to message #685956] Tue, 10 May 2022 13:44 Go to previous messageGo to next message
alcapps
Messages: 7
Registered: May 2022
Junior Member
also on the orasessiOn object they use set db = oraSessiOn.OpenDatabse(instance,userid,password)
Re: Excel 64 bit problem using [message #685958 is a reply to message #685957] Tue, 10 May 2022 13:45 Go to previous messageGo to next message
alcapps
Messages: 7
Registered: May 2022
Junior Member
Thanks for the quick reply. I did try that connection but the OraSession has many other uses in the vba code seems like a full rewrite to get this converted to olddb.
Re: Excel 64 bit problem using [message #685959 is a reply to message #685958] Tue, 10 May 2022 13:55 Go to previous messageGo to next message
Michel Cadot
Messages: 68216
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

Correct! The procedures are not the same ones, this is a full rewrite.

The other option is to access your 19c database only from a 11.2.0.4 client using OO4O but you won't have any support from Oracle neither for 0040 nor for the 11gR2->19c interoperability (unless you have a Market-Driven Support contract for this later, see MOS note 207303.1).
Note this option will no more work with later versions (21c+).

Re: Excel 64 bit problem using [message #685961 is a reply to message #685959] Tue, 10 May 2022 14:32 Go to previous messageGo to next message
alcapps
Messages: 7
Registered: May 2022
Junior Member
what about db.Parameters.add "vendorxxx","" , 1

db was defined as set db = OraSessiOn.OpenDatabase(instance, userid, password, &0) Not sure how they were used.
Re: Excel 64 bit problem using [message #685962 is a reply to message #685961] Tue, 10 May 2022 14:33 Go to previous messageGo to next message
alcapps
Messages: 7
Registered: May 2022
Junior Member
what is the equivalent of this oracle session variable to ADODB?
Re: Excel 64 bit problem using [message #685963 is a reply to message #685962] Tue, 10 May 2022 14:33 Go to previous messageGo to next message
alcapps
Messages: 7
Registered: May 2022
Junior Member
Thanks for the help. I have the database being read now. Its in the weeds of the add parameters and such now.
Re: Excel 64 bit problem using [message #685964 is a reply to message #685963] Tue, 10 May 2022 14:39 Go to previous message
alcapps
Messages: 7
Registered: May 2022
Junior Member
I am coming across db.paarameters("itemx").value = "org_id" then
set = oradynaset = db.dbCreateDyaset(sql, O&)
Not sure what needs to happen for the recordset in adodb
Previous Topic: Error in writing to directory
Next Topic: Reinstall DATABASE 12C
Goto Forum:
  


Current Time: Thu Jun 30 11:29:59 CDT 2022