It maybe a dns issue, The below connection works because server "my-server"
Resolves in my land from "my-server" to "my-server.mycompany.com".
Driver={PostgreSQL
ANSI};Server=my-server;Port=5432;Database=dbname;Uid=user;Pwd=password;BI=2;TextAsLongVarchar=1;UnknownSizes=2;UnknownsAsLongVarchar=1;UseServerSidePrepare=1;
Does this help?
Why not go DSN-less? (Put the connection string into an INI disturbed with the program?)
Otherwise, you will goto every computer and Update the DSN whenever the server or db name is changed
Thanks
Barry Bell, IT Department
Office: 954-429-3771 x267 Fax: 954-281-1464 email Barry_Bell@harte-hanks.com
-----Original Message-----
From: pgsql-odbc-owner@postgresql.org [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Rob Richardson
Sent: Wednesday, April 25, 2012 10:06 AM
To: pgsql-odbc@postgresql.org
Subject: [ODBC] How can I keep an OdbcDataAdapter from using fully qualified tble names?
Hello!
How can I keep an OdbcDataAdapter from insisting on the fully qualified table name?
In VS 2008, I am trying to use the System.Data.Odbc namespace to work with a
PostGres database. I don't want to use npgsql because I want to work with DSNs
so that I get the flexibility of changing databases without changing my
program.
When I use an OdbcCommandBuilder object to create the insert, update and delete
commands for me, the table names are fully qualified. For example, an insert
command might begin with "insert into MyDatabase.public.MyTable...". When I try
to use that, I get an exception thrown that complains that cross-database
references are not implemented (even though the connection I am using is to the
MyDatabase database).
So, I wrote a little function that converts a string containing
"MyDatabase.public.MyTable" into "MyTable", and use that to replace the fully
qualified name in the command text with the bare table name. But when it comes
to time to call the adapter's Update() method to add a new row into my table,
the first thing the adapter does is to change the bare table name back to the
full "MyDatabase.public.MyTable" name, and then I get the same exception.
Thank you very much.
RobR
--
Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc