Re: Can't connect to Oracle using MSDAORA OLE DB provider



On Sep 18, 10:53 am, Charles Hooper <hooperc2...@xxxxxxxxx> wrote:
On Sep 18, 10:07 am, Jojo <jojoh...@xxxxxxxxx> wrote:





On Sep 8, 6:58 pm, Brian Peasland <d...@xxxxxxxxxxxxxxxxxxx> wrote:
Jojo wrote:
We use 10.2 client + xp. It works on one 3 years old Dell computer but
it does not work on a new Lenovo computer. Just do not know which
change causes this problem.

Which version of XP? If anything other than XP Professional, then that
might be the cause of your problem....

HTH,
Brian

--
===================================================================

Brian Peasland
d...@xxxxxxxxxxxxxxxxxxxxxxx://www.peasland.net
It is XP Professional Ver. 2002 Service Pack 2.
This problem is still unsolved. We are frustrated here. Any new ideas?

You will want to make certain that you have the latest version of
MDAC:
http://msdn2.microsoft.com/en-us/data/aa937730.aspx

Note that Microsoft stopped distributing a wide variety of drivers in
the more recent MDAC releases, so I usually install MDAC 1.5 on new
client computers in addition to MDAC 2.8. You might want to switch to
using the OraOLEDB provider, rather than the Microsoft supplied
driver. The ConnectionString changes from:
"Provider=MSDAORA.1;User ID=MyUsername;Password=MyPassword;Data
Source=MySID"
-to-
"Provider=OraOLEDB.Oracle;User ID=MyUsername;Password=MyPassword;Data
Source=MySID"

Also, you will need to perform a Custom install of the Oracle 10.2
client so that the necessary driver files are copied to the client
computer.

Charles Hooper
IT Manager/Oracle DBA
K&M Machine-Fabricating, Inc.- Hide quoted text -

- Show quoted text -

Thanks. Is there known issue about the OraOLEDB driver? We are worried
about the data transfer speed.

.



Relevant Pages

  • Re: SQL Native Client vs SQL Server Driver
    ... On the blog for the SQL Native Client, you will find a lot of useful ... However, its biggest advantage is that unlike the MDAC, not only that you ... They won't be happy if you break something on their machine by installing ... a new application should always use the lasted driver if it can do ...
    (microsoft.public.sqlserver.odbc)
  • Re: Cant connect to Oracle using MSDAORA OLE DB provider
    ... the more recent MDAC releases, so I usually install MDAC 1.5 on new ... client computers in addition to MDAC 2.8. ... client so that the necessary driver files are copied to the client ...
    (comp.databases.oracle.misc)
  • Re: Cant connect to Oracle using MSDAORA OLE DB provider
    ... the more recent MDAC releases, so I usually install MDAC 1.5 on new ... client computers in addition to MDAC 2.8. ... client so that the necessary driver files are copied to the client ... Is there known issue about the OraOLEDB driver? ...
    (comp.databases.oracle.misc)
  • Re: SBS 2003 - SBS 2008 migration issues
    ... DHCP cannot work properly with the hyper-v role, and probably DNS, neither will the configuration wizards. ... clients losing the ability to use it after removing trend client, reseting winsock / removing network components / reinstalling teh client don't bring it back. ... When I add the 32 bit driver to the printer it simply tells me it's not a suitable driver, and to try adding the driver from a 32 bit client. ... If I install hyperV on the SBS 2008 will it run a win2k3 server? ...
    (microsoft.public.windows.server.sbs)
  • Re: [PATCH 0/5] improve i2c probing
    ... There is no way a client would survive a driver module cycling. ... > having to probe for them. ... discussing about adapters that didn't want to be probed, ...
    (Linux-Kernel)