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

The issue is that ADO.Net's OdbcDataAdapter object automatically expands the
table name "MyTable" into "MyDatabase.public.MyTable", and PostgreSQL cannot
handle that.

In PgAdmin, "insert into cycle (cycle) values ('Another cycle')" succeeds, but
"insert into Anneal.public.cycle (cycle) values ('Another one')" fails with the
cross-database references not implemented error.  The OdbcDataAdapter object
automatically converts a query of the first form into a query of the second
form, and I want to know how to stop it from doing that.

RobR