I can confirm the same problem on both a laptop running XP pro and on a server running Windows 2003 Server (Enterprise).
When I removed the R:base 7 (beta) from the laptop I was able to add System DSN's. Actually all the ones I tried to add when RB7 was there show up instantly after its removal. Support has referred me to a URL to download something that might help but we have had some password problems with that URL in the mean time. I don't want to take off RB7 from W2003 server due to the nature of the RB7 license. The problem does not seem to affect NT 4.0 server.
I will let you know If I come up with a fix.
~Cheers,
Brian Mowers
At 08:25 AM 10/28/2003, you wrote:
I have a brand new XP laptop, and have been installing software and
patches on it since Friday. I have a huge problem that has now consumed
about 24 hours. Have any of you fount a similar problem?
When I add a system data source through the Windows ODBC
Administrator, it never appears on the list, nor on the list of data sources in
the Dev Studio workspace. (If I try to recreate the same one, I get a prompt
that the name already exists, do I want to overwrite?)
The data source is working. A running application can connect to it and
query the data source. (Meanwhile, I can't do any development, because I
cannot "see" the datasource from Dev Studio, or even from the ODBC
Administrator. It is not just an Oterro problem: I cannot see ANY system data
source of Any kind in the ODBC Administrator list of System DSNs.
I have R:Tango 5.0, which includes Developers Studio 5.0 and the R:Base
Technologies' Oterro ODBC driver.
I have installed MS MDAC 2.8, which includes the latest ODBC Administrator
3.525.1022.0. I had the problem before I installed that, and installing it did
not fix the problem.
I have tried MSKB article 285654 on the ListSystemDSNs registry key, that's
not it, there is no such registry key in my registry. (I suspected that one,
because i did install IIS on the laptop for testing.)
[EMAIL PROTECTED]
