>Yep. I made that mistake first and then hit my head against the wall thinking how stupid I was. I quickly fixed that error, or so I thought. I have Net*8 client installed on the (web) server with correctly configured tnsnames.ora. All the components are running on this server.
>
>The following scenarios work:
>
>(1) sit at web server console and try to connect using SQL*Plus
>(2) sit at web server console, set up ODBC DSN using MS ODBC driver and Oracle ODBC Test
>(3) re-code application to use Oracle ODBC driver instead and access it via IE from a workstation (I think it works - I am getting other errors that could just be my App)
>
>The following scenario does not work:
>
>(1) Application using Micorosft ODBC driver connecting via IE from workstation.
>
>I suppose if I have to I can re-write the app using the Oracle driver, but I would prefer not to. I have had too many bad experiences with their drivers in the past, and I now know the MS one pretty well. .
>
>My guess is the MS driver looks for the Oracle client DLLs in a different path/search order from the Oracle drivers. Possibly this is done on a per-user basis?
>
>Any suggestions?

I would seriously doubt the MS ODBC Driver looks for any Oracle client DLLs. The MS Driver would use its own.

The problem may be how you designed the COM object to use the drivers from IE. My experience is very limited here. I use Web Connect, and I use that interface to call VFP functions that would in turn use ODBC and DSN connections to retrieve and return data back to the browser.

Mark McCasland
Midlothian, TX USA