Peter, you rock! I installed the MyODBC driver under the admin account
and it worked! That makes sense. I guess I needed someone to point out
the somewhat-obvious. :)
From: Peter Carter [mailto:peterc@stripped]
Sent: Friday, June 13, 2003 7:17 AM
To: Gonzalez, Juan
Subject: RE: ambiguous results on connect
The only other thing would be READ/EXECUTE access to the actual driver
dll. Did you install it as administrator or your own account?
The only other thing to try is to re-install mdac / myodbc to fix
You've got a good one.
Quoting "Gonzalez, Juan" <JGonzalez@stripped>:
> Yes, it is a System DSN.
> -----Mensaje original-----
> De: Peter Carter [mailto:peterc@stripped]
> Enviado el: Viernes, 13 de Junio de 2003 11:02 a.m.
> Para: Gonzalez, Juan
> CC: myodbc@stripped
> Asunto: RE: ambiguous results on connect
> Is your DSN a system DSN? If not, it needs to be. The webserver run's
> as a different user. This is normal.
> Quoting "Gonzalez, Juan" <JGonzalez@stripped>:
> > Today I have more information about this problem.
> > I install myodbc 3.51 driver and define a System DSN.
> > The results are the same as with 2.x version.
> > I run the test from the DSN configuration and connect successfully,
> > but
> > ASP page (below you see the code) the message is the same: Provider
> > not found.
> MySQL ODBC Mailing List
> For list archives: http://lists.mysql.com/myodbc
> To unsubscribe:
This mail sent through IMP: http://mail.pbc.ottawa.on.ca
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc