I had this problem and it was due to the DSN being case sensitive. My database instance was called tigger, and I had specified it as tigger (lower case) during installation. However, the install subtly munches it to upper-case without making it obvious that it's done so and the Windows ODBC driver insists on it being supplied as uppercase. Try supplying the database name in uppercase on the connect dialog box.
> > Thanks for the quick response. The Windows machine > can see the Linux machine just fine - I can access the > database from the Windows machine using the Database > Manager gui, and in fact the database I'm testing with [ ... ] > > running Debian Woody. For > > > the most part, it runs fine but I can't access my > > database from SQL > > > Studio (on a Windows machine), web SQL studio or > > ODBC (local or > > > remote). I get this error from a local Web SQL: > > > > > > ODBC-Error: [SAP AG][LIBSQLOD SO][SAP DB]Unable to > > connect to data > > > source;-709 CONNECT: (database not running). > > return-code: SQL_ERROR > > > (-709). [ ... ] _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
