James Puddicombe
|
| Posted: 05/07/2003, 3:54 PM |
|
I was unable to access any DSN via ODBC from within CodeCharge (having tried to uninstall CodeCharge in order to get round latest Critical Update/CodeCharge issue)
(Running Windows XP Pro)
So I:
1) uninstalled CodeCharge
2) uninstalled MySQL ODBC v3.51 driver
3) Rebooted
4) Reinstalled MDAC 2.7
5) Rebooted
6) Reinstalled MySQL ODBC V3.51
7) Rebooted
8) Reinstalled CodeCharge 2.5.3
9) Reinstalled patch
Still CodeCharge reacts adversely:
- create new site
- select PHP 4.0 & Templates
- goto Database
- select 'DSN'
- select a previously defined ODBC source
- press the yellow database symbol, popping up the ODBC Data Source Adminstrator
- select my ODBC entry, and then click on configure
- Now have "MySQL ODBC 3.51 driver - DSN configuration" box open
- click on 'Test Data Source'
- RESULT: error box pops up:
title: MySQL ODBC 3.51 Driver, Version 03.51.03
main message: [MySQL][ODBC 3.51 Driver] Can't connect to MySQL Server on 'my sql machines IP address' (10061)
So of course I think - it's a problem with my own ODBC connection. So I open up control panel -> Administrative Tools -> Data sources and get to the ODBC connection again, from outside CodeCharge. I click 'Test Data Source' and voila - it works fine!
In other words, connecting to any of my ODBC sources from INSIDE CodeCharge now fails, whereas OUTSIDE CodeCharge (e.g. through Microsoft Access, or directly from the Data Sources box), they work just fine.
In all this have I managed to corrupt a data component of CodeCharge, which has not been corrected through reinstallation?
|
|
|
 |
RipCurl
|
| Posted: 05/07/2003, 4:58 PM |
|
I had a similar problem and I worked it out; dont have the work around here, but I'll post on how to do it. It was giving me problems as well, until i fixed my build i ODBC through CC
|
|
|
|
|
