>Hi Mark,
>
>In your Knowledge Base article on Configuring Your System for Access to Oracle, the MS ODBC driver is the recommended driver for connecting to Oracle.
>
>My client will want some specific reasons before dropping the default Oracle ODBC driver that comes with the Oracle software.
>
>Any help would be appreciated.
>
>Paul

I have experienced fewer data retrieval errors with the MS drivers. I also had problems if I had to join tables on more than 1 field. I have not tried the recent Oracle drivers so this may not be the case. However, I am so entrenched in the use of the MS drivers, I can not afford to switch at this point.

I also keep in mind that I am using a MS front-end [VFP] so I want to use a MS driver that will correctly interpret my VFP SQL syntax and translate it to the corresponding Oracle SQL syntax. I know MS has specifically developed their Oracle ODBC driver to do this. On the other hand, Oracle did not specifically develop their drivers for VFP [or any other MS SQL] syntax. Most assuredly, Oracle did develop their drivers with all their development products in mind. That may be a totally irrational arguement, but, so far, all is working reasonably well.

I have worked around those few things that do not work. Stuff that does not work include trying to parameterize the list in an IN clause or INLIST function. But this problem will not be unique to the MS drivers. There are also som screwy things with VARCHAR fields and how to handle them on the VFP side. Do a search on VARCHAR to find info about a MS KB article on this. This problem will also not be limited to the MS drivers.