I'm developing on XP SP1 platform.

I've downloaded today the 3.51.10-2 version and installed it; driver files are dated 18/Dec/04 (by the
way, this version was NOT on the website yesterday).
Before this I was working with a 3.51.10 October version, the one with not-storing-port bug.

With this new version I can't connect to MySQL using ODBC DSNs, getting a message stating:
"Could not determine the driver name so could not lookup setup library."

Checked the registry and everything is in place in both ODBC.INI and ODBCINST.INI keys, subkeys and values.

I'm developing a VC++ app that connected fine with the previous version and my connection string was just:
"DSN=Xpto;Database=xpto;"

The driver figured out the remaining parameters from the DSN.

Went backto code and appended on the connection string:
"DRIVER=MySQL ODBC 3.51 Driver;"
Error message now changed to: "Could not determine the file name of setup library."
Looks like it now knows the driver but cannot determine the reamining DSN parameters neither the driver setup from registry values (which is probably needed to ask the user for the lacking parameters).

Hardcoded all the parameters on the connection string and voilá: connection is successful.
But it's not what I want: I need DSN.
Also tried to link tables on MSAccess and got the "...not determine driver name..." error.

Hope this gets fixed up soon.
Regards, Fernando.

-----------------------------------
Chegou o Clix Turbo ADSL a 8 Megas
Internet + Telefone sem assinatura telefónica
Saiba mais em http://adsl.clix.pt



--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc [at] m.gmane.org

=46ernando,

I assume you are using SQLDriverConnect but you do not say anything about t=
he
other args to this call. Have you tried; hwnd of 0 and prompt of
SQL_DRIVER_NOPROMPT along with your DSN based connection string?


On Thursday 06 January 2005 16:34, f.n.cristovao [at] clix.pt wrote:
> I'm developing on XP SP1 platform.
>
> I've downloaded today the 3.51.10-2 version and installed it; driver files
> are dated 18/Dec/04 (by the way, this version was NOT on the website
> yesterday).
> Before this I was working with a 3.51.10 October version, the one with
> not-storing-port bug.
>
> With this new version I can't connect to MySQL using ODBC DSNs, getting a
> message stating: "Could not determine the driver name so could not lookup
> setup library."
>
> Checked the registry and everything is in place in both ODBC.INI and
> ODBCINST.INI keys, subkeys and values.
>
> I'm developing a VC++ app that connected fine with the previous version a=
nd
> my connection string was just: "DSN=3DXpto;Database=3Dxpto;"
>
> The driver figured out the remaining parameters from the DSN.
>
> Went backto code and appended on the connection string:
> "DRIVER=3DMySQL ODBC 3.51 Driver;"
> Error message now changed to: "Could not determine the file name of setup
> library." Looks like it now knows the driver but cannot determine the
> reamining DSN parameters neither the driver setup from registry values
> (which is probably needed to ask the user for the lacking parameters).
>
> Hardcoded all the parameters on the connection string and voil=E1:
> connection is successful. But it's not what I want: I need DSN.
> Also tried to link tables on MSAccess and got the "...not determine driver
> name..." error.
>
> Hope this gets fixed up soon.
> Regards, Fernando.
>
> -----------------------------------
> Chegou o Clix Turbo ADSL a 8 Megas
> Internet + Telefone sem assinatura telef=F3nica
> Saiba mais em http://adsl.clix.pt

=2D-
Peter Harvey, Software Developer
MySQL AB, www.mysql.com

Are you MySQL certified? www.mysql.com/certification


--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=3Dgcdmo-myodbc [at] m.gmane.o rg

Hi! Thanks for answering.

I'm not direct calling ODBC: i'm using CDatabase::OpenEx and I don't use the ODBC cursor library.
The only OpenEx parameter that generates a different result is CDatabase::noOdbcDialog; the error message turns to: "Access denied for user 'ODBC' [at] 'localhost'(using password:NO)"
My guess is that the driver tried to connect but the DSN parameters were not used.

All ODBC apps are failing with the same error messages: Crystal Reports, Visual Basic, MSAccess, ... and all of them used to work with all the previous versions I tried (like 3.51.06 or 3.51.09).

Maybe be something on the driver itself related to work with DSN info.

Fernando.

> Fernando,

> I assume you are using SQLDriverConnect but you do not say anything about the
> other args to this call. Have you tried; hwnd of 0 and prompt of
> SQL_DRIVER_NOPROMPT along with your DSN based connection string?


> On Thursday 06 January 2005 16:34, f.n.cristovao [at] clix.pt wrote:
> > I'm developing on XP SP1 platform.
> >
> > I've downloaded today the 3.51.10-2 version and installed it; driver files
> > are dated 18/Dec/04 (by the way, this version was NOT on the website
> > yesterday).
> > Before this I was working with a 3.51.10 October version, the one with
> > not-storing-port bug.
> >
> > With this new version I can't connect to MySQL using ODBC DSNs, getting a
> > message stating: "Could not determine the driver name so could not lookup
> > setup library."
> >
> > Checked the registry and everything is in place in both ODBC.INI and
> > ODBCINST.INI keys, subkeys and values.
> >
> > I'm developing a VC++ app that connected fine with the previous version and
> > my connection string was just: "DSN=Xpto;Database=xpto;"
> >
> > The driver figured out the remaining parameters from the DSN.
> >
> > Went backto code and appended on the connection string:
> > "DRIVER=MySQL ODBC 3.51 Driver;"
> > Error message now changed to: "Could not determine the file name of setup
> > library." Looks like it now knows the driver but cannot determine the
> > reamining DSN parameters neither the driver setup from registry values
> > (which is probably needed to ask the user for the lacking parameters).
> >
> > Hardcoded all the parameters on the connection string and voilá:
> > connection is successful. But it's not what I want: I need DSN.
> > Also tried to link tables on MSAccess and got the "...not determine driver
> > name..." error.
> >
> > Hope this gets fixed up soon.
> > Regards, Fernando.
> >
> > -----------------------------------
> > Chegou o Clix Turbo ADSL a 8 Megas
> > Internet + Telefone sem assinatura telefónica
> > Saiba mais em http://adsl.clix.pt

> --
> Peter Harvey, Software Developer
> MySQL AB, www.mysql.com

> Are you MySQL certified? www.mysql.com/certification




-----------------------------------
Chegou o Clix Turbo ADSL a 8 Megas
Internet + Telefone sem assinatura telefónica
Saiba mais em http://adsl.clix.pt



--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc [at] m.gmane.org

Can you please send a small example program which demonstrates the problem=

(the C test code I have here seems to work fine). We can use your test code=

and trace the problem.

Thanks


On Friday 07 January 2005 02:41, f.n.cristovao [at] clix.pt wrote:
> Hi! Thanks for answering.
>
> I'm not direct calling ODBC: i'm using CDatabase::OpenEx and I don't use
> the ODBC cursor library. The only OpenEx parameter that generates a
> different result is CDatabase::noOdbcDialog; the error message turns to:
> "Access denied for user 'ODBC' [at] 'localhost'(using password:NO)" My guess is
> that the driver tried to connect but the DSN parameters were not used.
>
> All ODBC apps are failing with the same error messages: Crystal Reports,
> Visual Basic, MSAccess, ... and all of them used to work with all the
> previous versions I tried (like 3.51.06 or 3.51.09).
>
> Maybe be something on the driver itself related to work with DSN info.
>
> Fernando.
>
> > Fernando,
> >
> > I assume you are using SQLDriverConnect but you do not say anything abo=
ut
> > the other args to this call. Have you tried; hwnd of 0 and prompt of
> > SQL_DRIVER_NOPROMPT along with your DSN based connection string?
> >
> > On Thursday 06 January 2005 16:34, f.n.cristovao [at] clix.pt wrote:
> > > I'm developing on XP SP1 platform.
> > >
> > > I've downloaded today the 3.51.10-2 version and installed it; driver
> > > files are dated 18/Dec/04 (by the way, this version was NOT on the
> > > website yesterday).
> > > Before this I was working with a 3.51.10 October version, the one with
> > > not-storing-port bug.
> > >
> > > With this new version I can't connect to MySQL using ODBC DSNs, getti=
ng
> > > a message stating: "Could not determine the driver name so could not
> > > lookup setup library."
> > >
> > > Checked the registry and everything is in place in both ODBC.INI and
> > > ODBCINST.INI keys, subkeys and values.
> > >
> > > I'm developing a VC++ app that connected fine with the previous versi=
on
> > > and my connection string was just: "DSN=3DXpto;Database=3Dxpto;"
> > >
> > > The driver figured out the remaining parameters from the DSN.
> > >
> > > Went backto code and appended on the connection string:
> > > "DRIVER=3DMySQL ODBC 3.51 Driver;"
> > > Error message now changed to: "Could not determine the file name of
> > > setup library." Looks like it now knows the driver but cannot determi=
ne
> > > the reamining DSN parameters neither the driver setup from registry
> > > values (which is probably needed to ask the user for the lacking
> > > parameters).
> > >
> > > Hardcoded all the parameters on the connection string and voil=E1:
> > > connection is successful. But it's not what I want: I need DSN.
> > > Also tried to link tables on MSAccess and got the "...not determine
> > > driver name..." error.
> > >
> > > Hope this gets fixed up soon.
> > > Regards, Fernando.
> > >
> > > -----------------------------------
> > > Chegou o Clix Turbo ADSL a 8 Megas
> > > Internet + Telefone sem assinatura telef=F3nica
> > > Saiba mais em http://adsl.clix.pt
> >
> > --
> > Peter Harvey, Software Developer
> > MySQL AB, www.mysql.com
> >
> > Are you MySQL certified? www.mysql.com/certification
>
> -----------------------------------
> Chegou o Clix Turbo ADSL a 8 Megas
> Internet + Telefone sem assinatura telef=F3nica
> Saiba mais em http://adsl.clix.pt

=2D-
Peter Harvey, Software Developer
MySQL AB, www.mysql.com

Are you MySQL certified? www.mysql.com/certification


--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=3Dgcdmo-myodbc [at] m.gmane.o rg

(In response to news:20050107104107.12115.qmail [at] maboque.srv.clix.pt by )

> Maybe be something on the driver itself related to work with DSN info.

Hello Fernando,

Just had the exact same message as you have, stumbled upon your message. I
have found a workaround and would like to let you know:

You have to create System Data Sources as the user that installed ODBC
drivers, then they will work.

Sorry for barging in if this does not help you or if you already did try
that.

kaspar

hand manufactured code - www.tua.ch/ruby


--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc [at] m.gmane.org

Hi Kaspar.

You have helped me indeed. I've been sending Peter Harvey debug messages and details, he produced 2 patches but the bug is still there and I still couldn't connect until I saw your reply.

Curiously enough, what wou wrote was not the solution for me, because all the time I have been creating system DSNs as the user who installed the driver.
But your workaround inspired me to do the other way around: I went on creating a user DSN and voilá - connection successful!

So, now we know it is probably something related to access permissions to the DSN.

I guess now we have workarounds for the bug, but the bug is there and is not suitable for production releases of any kind and we hope this gets corrected asap (my current CV++ development needs to use a system DSN so all users can connect...).

Regards from Portugal
Fernando

> > Maybe be something on the driver itself related to work with DSN info.

> Hello Fernando,

> Just had the exact same message as you have, stumbled upon your message. I
> have found a workaround and would like to let you know:

> You have to create System Data Sources as the user that installed ODBC
> drivers, then they will work.

> Sorry for barging in if this does not help you or if you already did try
> that.

> kaspar

> hand manufactured code - www.tua.ch/ruby


> --
> MySQL ODBC Mailing List
> For list archives: http://lists.mysql.com/myodbc
> To unsubscribe: http://lists.mysql.com/myodbc?unsub=f.n.cristovao [at] clix.pt




-----------------------------------
Chegou o Clix Turbo ADSL a 8 Megas
Internet + Telefone sem assinatura telefónica
Saiba mais em http://adsl.clix.pt



--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc [at] m.gmane.org

(In response to news:20050115140601.9200.qmail [at] maboque.srv.clix.pt by )

> So, now we know it is probably something related to access permissions
> to the DSN.
>
> I guess now we have workarounds for the bug, but the bug is there and
> is not suitable for production releases of any kind and we hope this
> gets corrected asap (my current CV++ development needs to use a system
> DSN so all users can connect...).

Hey Fernando,

Glad I could help you. I definitly think its some kind of permission
issue, either on the actual .dll files or on the windows registry. I have
managed to create System DSN's here (windows XP), so everyone is happy at
my office, but tracking down why it worked could be real hard.

Maybe someone should look at the source and tell us what exact causes
there are for this somewhat cryptic error message. I agree with you that
this is not yet production quality code, as I expect System DSN's to
'just work'.

But nevertheless, it is great to have the code and to get it to work
somehow. So thank you anyways, creators of mysql ODBC ! ;)

best regards, kaspar

hand manufactured code - www.tua.ch/ruby


--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc [at] m.gmane.org

I have been trying to use DNSless connections, so this workaround didn't =
work for me. I have tried the two patches as well. I have ended up =
putting 4.51.09 back on until it gets resolved. I luckily had the old =
version stashed away. I could not find it in the archive download =
section.
Hope this helps.

Shane

-----Original Message-----
From: f.n.cristovao [at] clix.pt [mailto:f.n.cristovao [at] clix.pt]
Sent: Saturday, January 15, 2005 8:06 AM
To: myodbc [at] lists.mysql.com
Subject: Re: Re: Re: 3.51.10-2 DSNs fail connection


Hi Kaspar.

You have helped me indeed. I've been sending Peter Harvey debug messages =
and details, he produced 2 patches but the bug is still there and I =
still couldn't connect until I saw your reply.

Curiously enough, what wou wrote was not the solution for me, because =
all the time I have been creating system DSNs as the user who installed =
the driver.
But your workaround inspired me to do the other way around: I went on =
creating a user DSN and voil=E1 - connection successful!

So, now we know it is probably something related to access permissions =
to the DSN.

I guess now we have workarounds for the bug, but the bug is there and is =
not suitable for production releases of any kind and we hope this gets =
corrected asap (my current CV++ development needs to use a system DSN so =
all users can connect...).

Regards from Portugal
Fernando

--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=3Dgcdmo-myodbc [at] m.gmane.o rg

Hi All,
I've read that there a problem with MyODBC 3.51.10 but I have the
original version (maybe) which is not raise error like the other
complain and so far i use that MyODBC is OK. The filename is
MyODBC-3.51.10-x86-win-32bit.msi. Is this version you're all looking
at? If it can help I need a hosting because i don't have any hosting
to host these file so other can download it

Thanks
Best Regards,
Christian

--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc [at] m.gmane.org

3.51.10-2 seems to be having issues.
I'm using 3.51.09 without trouble so far.

-----Original Message-----
From: Christian Surya [mailto:csuryas [at] gmail.com]
Sent: Tuesday, January 18, 2005 12:00 AM
To: myodbc [at] lists.mysql.com
Subject: Re: Re: Re: 3.51.10-2 DSNs fail connection


Hi All,
I've read that there a problem with MyODBC 3.51.10 but I have the
original version (maybe) which is not raise error like the other
complain and so far i use that MyODBC is OK. The filename is
MyODBC-3.51.10-x86-win-32bit.msi. Is this version you're all looking
at? If it can help I need a hosting because i don't have any hosting
to host these file so other can download it

Thanks
Best Regards,
Christian

--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=3Dgcdmo-myodbc [at] m.gmane.o rg

my version is not 3.51.10-2. After I check the summary page in
properties of the installer, the revision number is
{247128D1-3769-4455-B27C-B68E0AA22A46}. is this revision number same
like your 3.51.10-2 if same so my myODBC is same version but if not
same then this is the first version of 3.51.10. if you need this
version mail me n i'll attach it to you


On Tue, 18 Jan 2005 08:27:48 -0600, Bumpurs, C. Shane (Getronics)
<BumpurCS [at] bp.com> wrote:
> 3.51.10-2 seems to be having issues.
> I'm using 3.51.09 without trouble so far.
>
> -----Original Message-----
> From: Christian Surya [mailto:csuryas [at] gmail.com]
> Sent: Tuesday, January 18, 2005 12:00 AM
> To: myodbc [at] lists.mysql.com
> Subject: Re: Re: Re: 3.51.10-2 DSNs fail connection
>
> Hi All,
> I've read that there a problem with MyODBC 3.51.10 but I have the
> original version (maybe) which is not raise error like the other
> complain and so far i use that MyODBC is OK. The filename is
> MyODBC-3.51.10-x86-win-32bit.msi. Is this version you're all looking
> at? If it can help I need a hosting because i don't have any hosting
> to host these file so other can download it
>
> Thanks
> Best Regards,
> Christian
>
> --
> MySQL ODBC Mailing List
> For list archives: http://lists.mysql.com/myodbc
> To unsubscribe: http://lists.mysql.com/myodbc?unsub=csuryas [at] gmail.com
>
>

--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc [at] m.gmane.org

Hi. I have it too and I'm using it while the bug isn't corrected.

The problem is that tis versoin that you and I have is bogus on other aspects (like it does not store port number on DSN config). This "-2" version was implemented to fix those bugs but it brought this new problem that we are all aware now.

Thank you anyway.
Regards, Fernando


> Hi All,
> I've read that there a problem with MyODBC 3.51.10 but I have the
> original version (maybe) which is not raise error like the other
> complain and so far i use that MyODBC is OK. The filename is
> MyODBC-3.51.10-x86-win-32bit.msi. Is this version you're all looking
> at? If it can help I need a hosting because i don't have any hosting
> to host these file so other can download it

> Thanks
> Best Regards,
> Christian

> --
> MySQL ODBC Mailing List
> For list archives: http://lists.mysql.com/myodbc
> To unsubscribe: http://lists.mysql.com/myodbc?unsub=f.n.cristovao [at] clix.pt




-----------------------------------
Chegou o Clix Turbo ADSL a 8 Megas
Internet + Telefone sem assinatura telefónica
Saiba mais em http://adsl.clix.pt



--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc [at] m.gmane.org

Hang in there guys - we are working on the fix for SQLDriverConnect and
should have a solution on www.mysql.com very soon.


f.n.cristovao [at] clix.pt wrote:

>Hi. I have it too and I'm using it while the bug isn't corrected.
>
>The problem is that tis versoin that you and I have is bogus on other aspects (like it does not store port number on DSN config). This "-2" version was implemented to fix those bugs but it brought this new problem that we are all aware now.
>
>Thank you anyway.
>Regards, Fernando
>
>
>


--
Peter Harvey, Software Developer
MySQL AB, www.mysql.com

Are you MySQL certified? www.mysql.com/certification



--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc [at] m.gmane.org