On Windows 2003 Server 2003+ Access, can"t connect to MyODBC

--------------030106090604090201010404
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable


Hello all:

I've installed a server with Windows Server 2003 R2. I've installed=20
MyODBC and Access 2000 too. I created DSN's to MyODBC and 'test' is=20
correct. However, if I try link in a Access database this DSN's, Access=20
chash.

Before that, I installed an VMware machine with the same configuration,=20
except the Windows Server 2003, that was not 'R2'. All worked fine with=20
this configuration.

Have anybody experimented similar behavoiur?

Best regards.


-------------------------------
Jos=E9 Miguel Serrano


--------------030106090604090201010404--

RE: On Windows 2003 Server 2003+ Access, can"t connect to MyODBC

I had a problem similar to this at one of the clients that I am working =
with
about 2 weeks ago as they migrated from Windows NT 4.0 to Windows server
2003. Access was crashing everytime I tried to connect to MySQL. What I
wound up having to do was write an Access module that Programatically =
update
the tabledef's for the linked MySQL tables. =20


Thank you
=20
Eric H. Lommatsch
Programmer
MICRONix, Inc.
2087 South Grant Street
Denver, CO 80210
Tel 303-777-8939
Fax 303-778-0378
=20
ericl@Micronix.com

-----Original Message-----
From: Jos=E9 Miguel Serrano [mailto:jmserrano@ain.es]=20
Sent: Wednesday, May 03, 2006 1:41 AM
To: 'myodbc'
Subject: On Windows 2003 Server 2003+ Access, can't connect to MyODBC


Hello all:

I've installed a server with Windows Server 2003 R2. I've installed=20
MyODBC and Access 2000 too. I created DSN's to MyODBC and 'test' is=20
correct. However, if I try link in a Access database this DSN's, Access
chash.

Before that, I installed an VMware machine with the same configuration,
except the Windows Server 2003, that was not 'R2'. All worked fine with =
this
configuration.

Have anybody experimented similar behavoiur?

Best regards.


-------------------------------
Jos=E9 Miguel Serrano




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

Re: On Windows 2003 Server 2003+ Access, can"t connect to MyODBC

--------------060302060509010008000407
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable


Hello David, and hello all:

I've tried with both versions 3.51.11-2 - 3.51.12, and in both Access=20
crash. Versions of Access were 2000, and XP .
Where I can download 3.51.13 version?. I've looked for in MySQL site,=20
but I haven't had success.

Thanks in advance,

Jos=E9 Miguel Serrano


---------------------------
David Dindorp escribi=F3:
>> if I try link in a Access database this DSN's, Access chash.
>> Have anybody experimented similar behavoiur?
>
> You neglected to mention which version of MyODBC you're using.
> The 3.51.13 prerelease is known to be buggy.


--------------060302060509010008000407--

Re: On Windows 2003 Server 2003+ Access, can"t connect to MyODBC

José Miguel Serrano wrote:
>
> Hello all:
>
> I've installed a server with Windows Server 2003 R2. I've installed
> MyODBC and Access 2000 too. I created DSN's to MyODBC and 'test' is
> correct. However, if I try link in a Access database this DSN's,
> Access chash.

This is a long-standing bug:
http://bugs.mysql.com/bug.php?id=9932

The best work-around I found was posted by Jean-Nicholas Harvey,
half-way down the page. It sounds strange, but it works :)

I await a proper solution.

--
Daniel Kasak
IT Developer
NUS Consulting Group
Level 5, 77 Pacific Highway
North Sydney, NSW, Australia 2060
T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989
email: dkasak@nusconsulting.com.au
website: http://www.nusconsulting.com.au

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

Re: On Windows 2003 Server 2003+ Access, can"t connect to MyODBC

--------------050409080105090601090103
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable


UAUHHHHHHHHHHHH !! It sounds that is the solution. I run to try it just =

now !!

Thanks to Daniel, Enrico, and all people. I'm asking myself, if SP1, or=20
'R2' release of Windows Server 2003 is a "MALICIOUS=20
code".................. What do you think about this? If so, is this a=20
legal practice? If I'm not wrong, now in Europe, Microsoft is having a=20
legal action for monopolistic practices.

Best regards,

Jos=E9 Miguel Serrano

--------------050409080105090601090103--

Re: On Windows 2003 Server 2003+ Access, can"t connect to MyODBC

José Miguel Serrano wrote:

> I'm asking myself, if SP1, or 'R2' release of Windows Server 2003 is a
> "MALICIOUS code".................. What do you think about this? If
> so, is this a legal practice?

On one hand, I wouldn't be particularly surprised if this were a
deliberate move to break certain software. Of course this is just
conjecture. I don't know. I know the change has happened
across-the-board ... it's not just W2K3 server affected - certainly W2K
as well.

But on the other hand, how long ago did this happen? The bug was
reported in August, 2005.

--
Daniel Kasak
IT Developer
NUS Consulting Group
Level 5, 77 Pacific Highway
North Sydney, NSW, Australia 2060
T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989
email: dkasak@nusconsulting.com.au
website: http://www.nusconsulting.com.au

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

Re: On Windows 2003 Server 2003+ Access, can"t connect to MyODBC

--------------050201010805040808080900
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable


I tried Enrico's suggestion, and Access work fine at last.

Thanks everybody.

Regards, and good weekend,


--------------------------------------------
Jos=E9 Miguel Serrano


--------------050201010805040808080900--