Re: Problems with ODBC Driver

Started by Hiroshi Saitoover 15 years ago4 messagesgeneral
Jump to latest
#1Hiroshi Saito
z-saito@guitar.ocn.ne.jp

Hi.

There is very little information which explores a problem.
What thing is an actual error message?

The following is my imagination....
As for specific field, it may be the LOWER problem of a character.

example)
-- CREATE TABLE xx("Field" TEXT);

postgres=# SELECT Field FROM xx;
ERROR: column "field" does not exist
LINE 1: SELECT Field FROM xx;

postgres=# SELECT "Field" FROM xx;
Field
-------
(0 rows)

If my misunderstand, the error message which you show will be able to be solved.

Regards,
Hiroshi Saito

----- Original Message -----
From: "Phil Jackson" <sapient@clear.net.nz>

Show quoted text

I have a notebook that I am using as a server for testing purposes and
it has the official ODBC driver installed. I can access this and use it
connect to PostreSql.

On a second machine on the same network - I also have the same ODBC
driver installed.

The behaviour of this one is quite different.

I have a test program that works on the server but when I run it on this
workstation, it can create a file with a couple of fields which I can
verify by looking inside PostgreSQL. But when I go to open up that file
and refer to one of its fields, I get an error message saying the field
doesn't exist.

I am running XP Professional on both machines.

I have no idea what is happening - I have opened up the firewall on both
machines to allow port 5432 to be used by all applications with TCP
(also tried TCP and UDP).

Does anyone have any suggestions?

Cheers

Phil Jackson

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

#2Joshua D. Drake
jd@commandprompt.com
In reply to: Hiroshi Saito (#1)

On Thu, 2010-09-02 at 14:04 +1200, Phil Jackson wrote:

Does anyone have any suggestions?

What does the ODBC log say?
What does the PostgreSQL Log (or event viewer) say?

JD

Cheers

Phil Jackson

--
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579
Consulting, Training, Support, Custom Development, Engineering
http://twitter.com/cmdpromptinc | http://identi.ca/commandprompt

#3Hiroshi Saito
z-saito@guitar.ocn.ne.jp
In reply to: Hiroshi Saito (#1)

Hi.

Um, it is very strange.
Can you send us the mylog of psqlODBC?

Regards,
Hiroshi Saito

Show quoted text

Hi Hiroshi

The same program works on the server unchanged - that's why I think it
is something to do with the driver. The error message says that the
field name doesn't exist when it does as can be verified by looking at
the database in Postgresql.

Cheers

Phil Jackson
On 9/2/2010 3:19 AM, Hiroshi Saito wrote:

Hi.

There is very little information which explores a problem. What thing
is an actual error message?
The following is my imagination....
As for specific field, it may be the LOWER problem of a character.
example)
-- CREATE TABLE xx("Field" TEXT);

postgres=# SELECT Field FROM xx;
ERROR: column "field" does not exist
LINE 1: SELECT Field FROM xx;

postgres=# SELECT "Field" FROM xx;
Field
-------
(0 rows)

If my misunderstand, the error message which you show will be able to
be solved.
Regards,
Hiroshi Saito

----- Original Message ----- From: "Phil Jackson" <sapient@clear.net.nz>

I have a notebook that I am using as a server for testing purposes
and it has the official ODBC driver installed. I can access this and
use it connect to PostreSql.

On a second machine on the same network - I also have the same ODBC
driver installed.

The behaviour of this one is quite different.

I have a test program that works on the server but when I run it on
this workstation, it can create a file with a couple of fields which
I can verify by looking inside PostgreSQL. But when I go to open up
that file and refer to one of its fields, I get an error message
saying the field doesn't exist.

I am running XP Professional on both machines.

I have no idea what is happening - I have opened up the firewall on
both machines to allow port 5432 to be used by all applications with
TCP (also tried TCP and UDP).

Does anyone have any suggestions?

Cheers

Phil Jackson

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

#4Phil Jackson
sapient@clear.net.nz
In reply to: Hiroshi Saito (#1)
Problems with ODBC Driver

Hi Hiroshi

The same program works on the server unchanged - that's why I think it
is something to do with the driver. The error message says that the
field name doesn't exist when it does as can be verified by looking at
the database in Postgresql.

Cheers

Phil Jackson

Show quoted text

On 9/2/2010 3:19 AM, Hiroshi Saito wrote:

Hi.

There is very little information which explores a problem. What thing
is an actual error message?
The following is my imagination....
As for specific field, it may be the LOWER problem of a character.
example)
-- CREATE TABLE xx("Field" TEXT);

postgres=# SELECT Field FROM xx;
ERROR: column "field" does not exist
LINE 1: SELECT Field FROM xx;

postgres=# SELECT "Field" FROM xx;
Field
-------
(0 rows)

If my misunderstand, the error message which you show will be able to
be solved.
Regards,
Hiroshi Saito

----- Original Message ----- From: "Phil Jackson" <sapient@clear.net.nz>

I have a notebook that I am using as a server for testing purposes
and it has the official ODBC driver installed. I can access this and
use it connect to PostreSql.

On a second machine on the same network - I also have the same ODBC
driver installed.

The behaviour of this one is quite different.

I have a test program that works on the server but when I run it on
this workstation, it can create a file with a couple of fields which
I can verify by looking inside PostgreSQL. But when I go to open up
that file and refer to one of its fields, I get an error message
saying the field doesn't exist.

I am running XP Professional on both machines.

I have no idea what is happening - I have opened up the firewall on
both machines to allow port 5432 to be used by all applications with
TCP (also tried TCP and UDP).

Does anyone have any suggestions?

Cheers

Phil Jackson

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