Re: How can I keep an OdbcDataAdapter from using fully qualified tble names?

Your SQL"select * from DBNAME.TABLENAME"
Instead of just " select * from TABLENAME" ?

Does the user use a different DB Login then you do?
Try logging as the user into pgadmin and run the SQL.

If you have the same issues, the issue is with the user access rights (or under which right a view/table was created).

Thanks
Barry Bell, IT Department
Office: 954-429-3771 x267 Fax: 954-281-1464 email Barry_Bell(at)harte-hanks(dot)com

-----Original Message-----
From: pgsql-odbc-owner(at)postgresql(dot)org [mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Rob Richardson
Sent: Wednesday, April 25, 2012 10:25 AM
To: pgsql-odbc(at)postgresql(dot)org
Subject: Re: [ODBC] How can I keep an OdbcDataAdapter from using fully qualified tble names?

I want to stick with DSNs because we change databases frequently, mainly on our own systems. Develop first using a test database, then do final testing on a copy of the customer's production database, then, if problems crop up, get an up-to-date copy of the customer's database and debug using that. That's what DSNs are for. They work. (At least until the .Net world apparently decided it knows better.)

I think you're thinking of a different issue. I'm not talking about a fully qualified name of a server, with "mycompany.com" appended to it. I'm talking about a fully qualified table name, with the database name and schema prepended to it.

RobR

--
Sent via pgsql-odbc mailing list (pgsql-odbc(at)postgresql(dot)org) To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc