Bill,

Do you have Rbase 7.0 installed.  I ran into the same problem after
installing Rbase 7.0 but before installing Witango or any other software.
The problem went away after I uninstalled Rbase 7.0.  Try uninstalling Rbase
7.0

Ted

-----Original Message-----
From: Bill Downall [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, October 28, 2003 8:26 AM
To: RBase List Server; [EMAIL PROTECTED]
Subject: Witango-Talk: Win XP ODBC System DSN problem


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.)




________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf

Reply via email to