Rowland, possibly you have your answer already. I recall that you are on a Mac?
IP 127.0.0.1 is your own computer's IP. Is that the correct MySQL host? Sounds like your host (that you are using ODBC for) is remote. If so, the IP would be different. Sincerely, Rodney Schmidt > From: Rowland & Wilma Carson <[EMAIL PROTECTED]> > Reply-To: "Claris FileMaker Pro discussions <[email protected]>" > <[email protected]> > Date: Mon, 10 Nov 2008 19:18:06 +0000 > To: "Claris FileMaker Pro discussions <[email protected]>" > <[email protected]> > Subject: Re: ODBC error question > > At 2008-11-09 18:16 -0800 John Weinshel wrote: > >> my memory is that there was a problem with some of >> the later MySQL drivers on the Windows side > >> Try installing the earlier driver and setting >> up your DSN pointing to it. > > John - thanks for the suggestion. I tried the earlier driver but it > doesn't work at all - the test button fails. I think that one may be > for earlier versons of MySQL as it was a MySQL error that the test > button returned. The server is running MySQL 5. I had configured the > DSN before going online (yes, I'm STILL on dial-up) and when I tried > to use it with FMP I got a similar error to the previous attempt: > > "ODBC Error: [MySQL][ODBC 3.51 Driver]Can't connect to MySQL server on > '127.0.0.1' (10061)". > > Note that the host is identified in this mssage by IP number rather > than by name, which may be a clue. I recall that somewhere it says > it's essential to quote the IP number rather than the name when > setting up these DSNs, and that's what I did for the original one. > Despite that, the FMP error message refers to it as 'localhost'. I've > checked again and the DSN config definitely specifies 127.0.0.1, not > localhost - and when I test it offline, it returns an error saying it > couldn't connect to MySQL server on 127.0.0.1. > > Strangely, the official FMP advice for Windows is to use > Connector/ODBC v3.51.14, but the earliest I could find for download > is v3.51.26. (And for the Mac, FMP specifies the Actual driver v2.7, > whereas the version currently sold & working fine for me is v2.8d.) > > The really irritating thing is that this WAS working. I know > something must have changed, but the only thing I've done that might > conceivably affect it is to install a USB ADSL modem driver for BT > broadband. Can't see any part of its preferences that could cause > this sort of problem, though. > > Thanks again. > > regards > > Rowland > -- > | Wilma & Rowland Carson http://home.clara.net/rowil/ > | <[EMAIL PROTECTED]> ... that's Rowland with a 'w' ...
