Re: Problem using FoxPro OLE DB Connection

microsoft.public.inetserver.asp.general

14 Mar 2005 6:53 PM

rajy

Hi Dave Anderson,

I happened to see your post re an OLEDB-Oracle error that you mentioned in
one of your posts.

I summarise the issue that I have as follows

1) I wrote a VB component, which connects to an Oracle DB and does some data
retrieval and updates
2) This component is instantiated in ASP page and when the ASP page runs it
gives the following error, "Error 3706: Provider cannot be found. It may not
be properly installed."
3) I am using cnDB.Open "Provider=OraOLEDB.Oracle;Data Source=111;User
Id=111;Password=111;" and i have checked that the VB COM works when called
within a VB program
4) considering that VB COM connects to the Oracle DB successfully when
instantiated from VB, I am not sure why it does not work from ASP.
FYI, I'm running Oracle 9.2, MDAC 2.8, WInXP service pack 1.; uisng local
IIS (developer workstation)
Would really appreciate any help.
Thanks
Rajy

Show quote

"Dave Anderson" wrote:

> Dr. Know wrote:
> > The wizard creates this connection string:
> > (which differs little from my original string)
> >
> > Provider=VFPOLEDB.1;Data Source=C:\DB2\DDMS;Password="";Collating
> > Sequence=MACHINE
> >
> > It tests OK in the wizard, but refuses to work in ASP - although it
> > and my original string work in VBA. Alternate DB formats, such as
> > MDB, also work fine...
>
> We had a similar problem with Oracle drivers above 9i, and the solution
> involved propagating permissions in the Oracle directory structure. The
> problem in that case was that IIS runs under a system account whose
> permissions are either not set up correctly by the Oracle installation, or
> were altogether nonexistent.
>
> If I had to guess at this point, I'd say you have a file permission problem.
>
>
>
> --
> Dave Anderson
>
> Unsolicited commercial email will be read at a cost of $500 per message. Use
> of this email address implies consent to these terms. Please do not contact
> me directly or ask me to contact you directly for assistance. If your
> question is worth asking, it's worth posting.
>
>
>