Connectivity Error

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Robert - 07 Jan 2005 00:49 GMT

Not sure if this is the proper place to ask this question.

Can anyone give some help on why I'm getting this error message? I am using
Windows XP Pro with Visual FoxPro 8 with Service pack 1. If I go to a PC
with Windows 98 Visual FoxPro 7 with Service Pack 1 I do not get this error
message.

"Connectivity Error[Microsoft][ODBC Driver Manager] data
source name not found and no default driver specified."

Reply to this Message

Stefan Wuebbe - 07 Jan 2005 10:44 GMT

Do you get the error running your own code or are you having
problems with a Vfp-based application written by somebody else?

In general, the message text sounds as if there were a Remote
View or an SPT connection failing to access an ODBC "DSN",
a "Data Souce Name".
You can avoid DSNs and subsequent additional maintenance by
using "DSN-less connections", see also
http://fox.wikis.com/wc.dll?Wiki~ProgrammaticallyCreatingDSNs~VFP
http://fox.wikis.com/wc.dll?Wiki~DirectODBCcalls~VFP
http://fox.wikis.com/wc.dll?Wiki~VFPCommandSQLStringConnect
http://groups.google.com/advanced_group_search

hth
-Stefan

> Not sure if this is the proper place to ask this question.
>
[quoted text clipped - 5 lines]
> "Connectivity Error[Microsoft][ODBC Driver Manager] data
> source name not found and no default driver specified."

Reply to this Message

Robert - 07 Jan 2005 13:15 GMT

This is from code that someone else wrote long before I came to work here.
It is from a remote view. The Vfp-based application was written by the same
person from what I understand.

> Do you get the error running your own code or are you having
> problems with a Vfp-based application written by somebody else?
[quoted text clipped - 21 lines]
> > "Connectivity Error[Microsoft][ODBC Driver Manager] data
> > source name not found and no default driver specified."

Reply to this Message

Stefan Wuebbe - 09 Jan 2005 12:19 GMT

When a remote view uses a DSN as connection, it will complain when
that DSN does not exist on the current machine -> Administrative
Tools -> Data Sources (ODBC)

You can improve the behaviour by re-designing the view using a
connection string instead of a DSN, for instance
cConnString = "DRIVER=SQL Server;Database=Northwind;" + ;
"APP=Microsoft(R) Windows NT(TM) Operating System;SERVER=(local)"
CREATE CONNECTION myConnection CONNSTRING m.cConnString

See also http://groups.google.com/advanced_group_search

hth
-Stefan

> This is from code that someone else wrote long before I came to work here.
> It is from a remote view. The Vfp-based application was written by the same
[quoted text clipped - 25 lines]
>> > "Connectivity Error[Microsoft][ODBC Driver Manager] data
>> > source name not found and no default driver specified."

Reply to this Message