pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feedODBC Problem
27+ messages / 22 participants
[nested] [flat]
* ODBC Problem
@ 1998-07-09 17:50 Len Morgan <len-morgan@xroadstx.com>
0 siblings, 2 replies; 27+ messages in thread
From: Len Morgan @ 1998-07-09 17:50 UTC (permalink / raw)
To: pgsql-interfaces
I have successfully connected to PostgreSQL from Access97 and have even been able to make a query that gets it's results from several tables all at once. The problem is that no matter what I do, the ORDER BY clause of the query is ignored. I have set the sort criteria and I have tried with a pass-through query but the sorting always seems to come out in the order of the subtables that are joined to my main table.
I also have had a problem where I want to write a pass-through query but can't get it to execute without bringing up the "Select Data Source" dialog box. We are only ever going to use one data source and I know what it is so why do I get this message EVERY time I run the query? Is there some way to specify the DSN in the pass-through query so that I don't have to have my users do this everytime?
Thanks for your help,
len morgan
^ permalink raw reply [nested|flat] 27+ messages in thread
* Re: [INTERFACES] ODBC Problem
@ 1998-07-10 16:03 Byron Nikolaidis <byronn@insightdist.com>
parent: Len Morgan <len-morgan@xroadstx.com>
1 sibling, 0 replies; 27+ messages in thread
From: Byron Nikolaidis @ 1998-07-10 16:03 UTC (permalink / raw)
To: Len Morgan <len-morgan@xroadstx.com>; +Cc: pgsql-interfaces
> Len Morgan wrote:
>
> I have successfully connected to PostgreSQL from Access97 and have
> even been able to make a query that gets it's results from several
> tables all at once. The problem is that no matter what I do, the
> ORDER BY clause of the query is ignored. I have set the sort criteria
> and I have tried with a pass-through query but the sorting always
> seems to come out in the order of the subtables that are joined to my
> main table.
>
I have had this problem also, but for the life of me, I can't reproduce
it now. I remember though, when I had the problem, if I turned on
"Totals" and just had "Group By" for all the fields, it allowed me to
order by whatever I wanted. It *seems* like a bug in Access? Try that
and see if it at least has an effect.
Also, what version of the odbc driver are you using? And, can you
illustrate your query (what tables, joins, etc) so I could try to
reproduce it?
> I also have had a problem where I want to write a pass-through query
> but can't get it to execute without bringing up the "Select Data
> Source" dialog box. We are only ever going to use one data source and
> I know what it is so why do I get this message EVERY time I run the
> query? Is there some way to specify the DSN in the pass-through query
> so that I don't have to have my users do this everytime?
>
Yes, I have this as well. I do not know any way to make Access save the
Data source with the query. As far as I can tell, it is not the driver
but Access forcing this behavior? Have you or anyone seen differently
with other databases like Oracle?
Byron
^ permalink raw reply [nested|flat] 27+ messages in thread
* Re: [INTERFACES] ODBC Problem
@ 1998-07-21 22:19 Byron Nikolaidis <byronn@insightdist.com>
parent: Len Morgan <len-morgan@xroadstx.com>
1 sibling, 0 replies; 27+ messages in thread
From: Byron Nikolaidis @ 1998-07-21 22:19 UTC (permalink / raw)
To: Len Morgan <len-morgan@xroadstx.com>; +Cc: pgsql-interfaces
> Len Morgan wrote:
>
> I have successfully connected to PostgreSQL from Access97 and have
> even been able to make a query that gets it's results from several
> tables all at once. The problem is that no matter what I do, the
> ORDER BY clause of the query is ignored. I have set the sort criteria
> and I have tried with a pass-through query but the sorting always
> seems to come out in the order of the subtables that are joined to my
> main table.
>
We have learned a few things about the Microsoft Jet Engine since this
mail. Access uses "dynasets" to handle data in query recordsets. If
you don't need to update values in your queries, you can use a
"snapshot" recordset, which can be faster. It also may help your
order-by random problem. To do this in Access, try bringing up the
"design view" of your query. Then right click and you should get a
"Query Properties" box. There is a field called "RecordSet Type" which
probably says Dynaset. If you set this to "Snapshot", your problem may
go away.
> I also have had a problem where I want to write a pass-through query
> but can't get it to execute without bringing up the "Select Data
> Source" dialog box. We are only ever going to use one data source and
> I know what it is so why do I get this message EVERY time I run the
> query? Is there some way to specify the DSN in the pass-through query
> so that I don't have to have my users do this everytime?
>
This one we definately have figured out. When looking at your pass-thru
query, go to "View" then "Properties" in Access. This will bring up a
box of properties. There is one called "ODBC Connect Str" and it should
be defaulted to "ODBC;". Simply add "DSN=<your_datasource>" after the
ODBC part and it won't keep asking you.
Hope this is helpful.
Byron
^ permalink raw reply [nested|flat] 27+ messages in thread
* ODBC problem
@ 1999-07-15 05:21 Terence Chan <kin.chan@technologist.com>
0 siblings, 1 reply; 27+ messages in thread
From: Terence Chan @ 1999-07-15 05:21 UTC (permalink / raw)
To: pgsql-interfaces
I have exported a table from MS Access 97 to PG via ODBC. I can see the file
is exported to the correct place but psql complaining the table is not
there.
Please help.
Terence
^ permalink raw reply [nested|flat] 27+ messages in thread
* Re: [INTERFACES] ODBC problem
@ 1999-07-15 06:14 Hannu Krosing <hannu@trust.ee>
parent: Terence Chan <kin.chan@technologist.com>
0 siblings, 1 reply; 27+ messages in thread
From: Hannu Krosing @ 1999-07-15 06:14 UTC (permalink / raw)
To: Terence Chan <kin.chan@technologist.com>; +Cc: pgsql-interfaces
Terence Chan wrote:
>
> I have exported a table from MS Access 97 to PG via ODBC. I can see the file
> is exported to the correct place but psql complaining the table is not
> there.
Are you sure that the file (and directories leading to it) are readable
by the
user postgres, or whatever your backend runs as ?
As a last resort move the file to /tmp and chmod 777 it.
------
Hannu
^ permalink raw reply [nested|flat] 27+ messages in thread
* RE: [INTERFACES] ODBC problem
@ 1999-07-15 06:22 Terence Chan <kin.chan@technologist.com>
parent: Hannu Krosing <hannu@trust.ee>
0 siblings, 0 replies; 27+ messages in thread
From: Terence Chan @ 1999-07-15 06:22 UTC (permalink / raw)
To: pgsql-interfaces
Thanks,
Yes, the file tblItem is belongs to user postgres. And I have also tried the
chmod 777 the file and still can't access it.
BTW, I can link / access the file from within MS Access via ODBC.
Any idea?
-----Original Message-----
From: hannu@kodu.home.ee [mailto:hannu@kodu.home.ee] On Behalf Of Hannu
Krosing
Sent: Thursday, July 15, 1999 2:14 PM
To: Terence Chan
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] ODBC problem
Terence Chan wrote:
>
> I have exported a table from MS Access 97 to PG via ODBC. I can see the
file
> is exported to the correct place but psql complaining the table is not
> there.
Are you sure that the file (and directories leading to it) are readable
by the
user postgres, or whatever your backend runs as ?
As a last resort move the file to /tmp and chmod 777 it.
------
Hannu
^ permalink raw reply [nested|flat] 27+ messages in thread
* [Fwd: [INTERFACES] ODBC problem]
@ 1999-07-15 13:49 Byron Nikolaidis <byronn@solipsys.com>
0 siblings, 0 replies; 27+ messages in thread
From: Byron Nikolaidis @ 1999-07-15 13:49 UTC (permalink / raw)
To: pgsql-interfaces
Terence Chan wrote:
> Thanks,
>
> Yes, the file tblItem is belongs to user postgres. And I have also tried the
> chmod 777 the file and still can't access it.
>
Its because the table is called "tblItem", notice the mixed case. If you want
to access this in pg, you need to use quotes around the table name to preserve
the case. The odbc does this for you.
Byron
^ permalink raw reply [nested|flat] 27+ messages in thread
* ODBC Problem
@ 2000-04-02 07:57 Albert J. Insogna <ainsogna@hotmail.com>
0 siblings, 1 reply; 27+ messages in thread
From: Albert J. Insogna @ 2000-04-02 07:57 UTC (permalink / raw)
To: pgsql-interfaces
Hello all,
Whenever I try and use ODBC to access my Postgres database through MS Access (or anything else), I am getting "Error #210 - Unsupported Front End Protocol". Any ideas? Thanks in advance...
Al Insogna
^ permalink raw reply [nested|flat] 27+ messages in thread
* Re: ODBC Problem
@ 2000-04-02 15:37 Thomas Lockhart <lockhart@alumni.caltech.edu>
parent: Albert J. Insogna <ainsogna@hotmail.com>
0 siblings, 0 replies; 27+ messages in thread
From: Thomas Lockhart @ 2000-04-02 15:37 UTC (permalink / raw)
To: Albert J. Insogna <ainsogna@hotmail.com>; +Cc: pgsql-interfaces
> Whenever I try and use ODBC to access my Postgres database
> through MS Access (or anything else), I am getting "Error #210 -
> Unsupported Front End Protocol". Any ideas? Thanks in advance...
You probably have a mismatch between versions. Make sure you are using
the latest release of both ODBC and Postgres, or be more specific
about which versions you *are* running...
- Thomas
--
Thomas Lockhart lockhart@alumni.caltech.edu
South Pasadena, California
^ permalink raw reply [nested|flat] 27+ messages in thread
* ODBC problem
@ 2000-10-07 09:02 George P. Esperanza <george@calamba.laguna.net>
0 siblings, 1 reply; 27+ messages in thread
From: George P. Esperanza @ 2000-10-07 09:02 UTC (permalink / raw)
To: pgsql-interfaces
Hi!
I'm using postgres 7.0.2 running in Linux. I tried to install Postgres
ODBC driver in my Windows95 PC just to test if i can connect to my
Postgres database using ODBC. I also downloaded ZEOS database explorer to
test if this will work. After configuring User DSN and Zeos Databse
Explorer Logon, i got this message:
Password Authentication failed for user 'user'
I tried other users and still the same problem. My Postgres is already
running with -i parameter (compiled with '--with-odbc') and i don't
have any problem accessing my database from another linux machine. I
checked Postgres log file and it shows the same message.
By the way, my Postgres server is configured to "crypt" authentication
type.
I'm planning to develop VB application that will use Postgres as my
database server.
Please advise.
Thanks
George
^ permalink raw reply [nested|flat] 27+ messages in thread
* Re: ODBC problem
@ 2000-10-07 14:31 Cedar Cox <cedarc@visionforisrael.com>
parent: George P. Esperanza <george@calamba.laguna.net>
0 siblings, 1 reply; 27+ messages in thread
From: Cedar Cox @ 2000-10-07 14:31 UTC (permalink / raw)
To: George P. Esperanza <george@calamba.laguna.net>; +Cc: pgsql-interfaces
> By the way, my Postgres server is configured to "crypt" authentication
> type.
That's the reason... My understanding is that there is no libcrypt for
win32 so the windows ODBC driver doesn't support crypt passwords. Allow
passwords in the clear (change 'crypt' to 'password' in pg_hba.conf) and
it should work fine. Of course this could be a security hole so be
careful what you do. Be sure to limit the IPs that are allowed to
connect.
Alternatively, you could do something I've thought about but never done
myself.. set up a ssh tunnel from the client to the server. I think this
can be done. Even if the ODBC driver did support crypt passwords, the sql
queries and responses could be picked up just as easily so there wouldn't
really be much of a security gain. If you're in an environment where
non-crypt passwords are a security risk, then ssh (or some other
encryption) is probably the way to go. Thoughts??
-Cedar
^ permalink raw reply [nested|flat] 27+ messages in thread
* Re: ODBC problem
@ 2000-10-08 23:53 Tom Samplonius <tom@sdf.com>
parent: Cedar Cox <cedarc@visionforisrael.com>
0 siblings, 1 reply; 27+ messages in thread
From: Tom Samplonius @ 2000-10-08 23:53 UTC (permalink / raw)
To: Cedar Cox <cedarc@visionforisrael.com>; +Cc: George P. Esperanza <george@calamba.laguna.net>; pgsql-interfaces
On Sat, 7 Oct 2000, Cedar Cox wrote:
> > By the way, my Postgres server is configured to "crypt" authentication
> > type.
>
> That's the reason... My understanding is that there is no libcrypt for
> win32 so the windows ODBC driver doesn't support crypt passwords. Allow
> passwords in the clear (change 'crypt' to 'password' in pg_hba.conf) and
> it should work fine. Of course this could be a security hole so be
> careful what you do. Be sure to limit the IPs that are allowed to
> connect.
Except for the fact that crypt provides little if no security increase.
Even though only a crypted password is sent over the wire, that crypted
password can still be captured off the wire and replayed to get access.
Plus crypt is a rather fast algorithm, making it easy to brute-force.
Of course, this is all pretty typical for databases. Most databases
transmit passwords in the clear. Some try a lame scramble, which is
trivial to unscramble and worse than crypt in that it is easy to reverse.
Even databases that don't transmit the password in the clear can by easily
broken by a replay attack, or if driver source is available, simply patch
the driver to accept already encrypted passwords.
Tom
^ permalink raw reply [nested|flat] 27+ messages in thread
* ODBC problem
@ 2000-10-09 09:52 soulimane sabir <sabirsou@caramail.com>
0 siblings, 0 replies; 27+ messages in thread
From: soulimane sabir @ 2000-10-09 09:52 UTC (permalink / raw)
To: pgsql-interfaces
Dear all
Does anyone know how to get the ODBC driver for Lotus
approach 3.0 ? I didn't find it in the web.
Thanks in advance.
Soulimane
______________________________________________________
Boîte aux lettres - Caramail - http://www.caramail.com
^ permalink raw reply [nested|flat] 27+ messages in thread
* Re: ODBC problem
@ 2000-10-09 16:32 Peter Eisentraut <peter_e@gmx.net>
parent: Tom Samplonius <tom@sdf.com>
0 siblings, 1 reply; 27+ messages in thread
From: Peter Eisentraut @ 2000-10-09 16:32 UTC (permalink / raw)
To: Tom Samplonius <tom@sdf.com>; +Cc: Cedar Cox <cedarc@visionforisrael.com>; George P. Esperanza <george@calamba.laguna.net>; pgsql-interfaces
Tom Samplonius writes:
> Except for the fact that crypt provides little if no security increase.
> Even though only a crypted password is sent over the wire, that crypted
> password can still be captured off the wire and replayed to get access.
Only if you happen to get the same salt from the server every time, which
is rather unlikely.
--
Peter Eisentraut peter_e@gmx.net http://yi.org/peter-e/
^ permalink raw reply [nested|flat] 27+ messages in thread
* Re: ODBC problem
@ 2000-10-09 16:45 Tom Lane <tgl@sss.pgh.pa.us>
parent: Peter Eisentraut <peter_e@gmx.net>
0 siblings, 0 replies; 27+ messages in thread
From: Tom Lane @ 2000-10-09 16:45 UTC (permalink / raw)
To: Peter Eisentraut <peter_e@gmx.net>; +Cc: Tom Samplonius <tom@sdf.com>; Cedar Cox <cedarc@visionforisrael.com>; George P. Esperanza <george@calamba.laguna.net>; pgsql-interfaces
Peter Eisentraut <peter_e@gmx.net> writes:
> Tom Samplonius writes:
>> Except for the fact that crypt provides little if no security increase.
>> Even though only a crypted password is sent over the wire, that crypted
>> password can still be captured off the wire and replayed to get access.
> Only if you happen to get the same salt from the server every time, which
> is rather unlikely.
However, the standard crypt algorithm only has a small number of
distinct salt values, so an attacker who's sniffed one login transaction
can connect repeatedly until challenged with the same salt he saw used
before.
We have talked about adding a higher-security login protocol --- you can
find past threads about this in the pghackers archive. IIRC a fairly
complete design was worked out, but no one's got round to implementing
it yet. There might still have been some unresolved objections, too.
regards, tom lane
^ permalink raw reply [nested|flat] 27+ messages in thread
* ODBC-Problem
@ 2001-01-01 03:49 Evil Azrael <EvilAzrael@EvilAzrael.de>
0 siblings, 1 reply; 27+ messages in thread
From: Evil Azrael @ 2001-01-01 03:49 UTC (permalink / raw)
To: pgsql-interfaces
HI
I have just moved my old MS Access Database to a postgres database via
odbc. all went okay, and i can access the database in MS Access via
ODBC. Only a Client programm that i wrote can´t access the database
anymore via ODBC. The Visual BAsic Database programm says that the
database itself is updateable, but the tables in it aren´t updateable,
and all tries to connect to a table in VB via the OpenRecordset method
fail with the error message "parse error near [name of the table]" or VB
tells that it´s a connection error.
That´s weird.
MS Access has no problems connecting and writing to the database.
VB´s Visual Database Manager can connect to the database, but can only
read tables.
MY VB programm can´t even connect to the tables, but it worked quite
good via ODBC to the Access Database.
I don´t know what i can anymore, so please help if you know a solution.
Christoph Nelles
^ permalink raw reply [nested|flat] 27+ messages in thread
* Re: ODBC-Problem
@ 2001-01-01 13:01 Evil Azrael <EvilAzrael@EvilAzrael.de>
parent: Evil Azrael <EvilAzrael@EvilAzrael.de>
0 siblings, 0 replies; 27+ messages in thread
From: Evil Azrael @ 2001-01-01 13:01 UTC (permalink / raw)
To: pgsql-interfaces
ok, i got a solution myself. i mistyped one tablename and wrote the
initial letter lower-case and it worked via odbc, even if i wroted the
name uppercase in VB. hm, that´s strange, should i post this behavior to
the bugs-mailinglist or is that behavior okay?
Christoph Nelles
Evil Azrael wrote:
>
> HI
>
> I have just moved my old MS Access Database to a postgres database via
> odbc. all went okay, and i can access the database in MS Access via
> ODBC. Only a Client programm that i wrote can´t access the database
> anymore via ODBC. The Visual BAsic Database programm says that the
> database itself is updateable, but the tables in it aren´t updateable,
> and all tries to connect to a table in VB via the OpenRecordset method
> fail with the error message "parse error near [name of the table]" or VB
> tells that it´s a connection error.
> That´s weird.
> MS Access has no problems connecting and writing to the database.
> VB´s Visual Database Manager can connect to the database, but can only
> read tables.
> MY VB programm can´t even connect to the tables, but it worked quite
> good via ODBC to the Access Database.
>
> I don´t know what i can anymore, so please help if you know a solution.
>
> Christoph Nelles
^ permalink raw reply [nested|flat] 27+ messages in thread
* RE: ODBC-Problem
@ 2001-01-03 00:54 Michael Davis <mdavis@sevainc.com>
0 siblings, 1 reply; 27+ messages in thread
From: Michael Davis @ 2001-01-03 00:54 UTC (permalink / raw)
To: pgsql-interfaces
Add a primary key index to the tables that you want to be able to update.
Access relies on the primary key for a lot of things. I recommend you add
a primary key to all postgres tables.
-----Original Message-----
From: Evil Azrael [SMTP:EvilAzrael@EvilAzrael.de]
Sent: Sunday, December 31, 2000 8:50 PM
To: pgsql-interfaces@postgresql.org
Subject: ODBC-Problem
HI
I have just moved my old MS Access Database to a postgres database via
odbc. all went okay, and i can access the database in MS Access via
ODBC. Only a Client programm that i wrote can?t access the database
anymore via ODBC. The Visual BAsic Database programm says that the
database itself is updateable, but the tables in it aren?t updateable,
and all tries to connect to a table in VB via the OpenRecordset method
fail with the error message "parse error near [name of the table]" or VB
tells that it?s a connection error.
That?s weird.
MS Access has no problems connecting and writing to the database.
VB?s Visual Database Manager can connect to the database, but can only
read tables.
MY VB programm can?t even connect to the tables, but it worked quite
good via ODBC to the Access Database.
I don?t know what i can anymore, so please help if you know a solution.
Christoph Nelles
^ permalink raw reply [nested|flat] 27+ messages in thread
* Re: RE: ODBC-Problem
@ 2001-01-03 14:01 Adam Lang <aalang@rutgersinsurance.com>
parent: Michael Davis <mdavis@sevainc.com>
0 siblings, 0 replies; 27+ messages in thread
From: Adam Lang @ 2001-01-03 14:01 UTC (permalink / raw)
To: pgsql-interfaces
Also, make sure the ODBC driver for postgres is set for updating. By
default it is read only.
Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
http://www.rutgersinsurance.com
----- Original Message -----
From: "Michael Davis" <mdavis@sevainc.com>
To: <pgsql-interfaces@postgresql.org>
Sent: Tuesday, January 02, 2001 7:54 PM
Subject: [INTERFACES] RE: ODBC-Problem
> Add a primary key index to the tables that you want to be able to update.
> Access relies on the primary key for a lot of things. I recommend you
add
> a primary key to all postgres tables.
>
> -----Original Message-----
> From: Evil Azrael [SMTP:EvilAzrael@EvilAzrael.de]
> Sent: Sunday, December 31, 2000 8:50 PM
> To: pgsql-interfaces@postgresql.org
> Subject: ODBC-Problem
>
> HI
>
> I have just moved my old MS Access Database to a postgres database via
> odbc. all went okay, and i can access the database in MS Access via
> ODBC. Only a Client programm that i wrote can?t access the database
> anymore via ODBC. The Visual BAsic Database programm says that the
> database itself is updateable, but the tables in it aren?t updateable,
> and all tries to connect to a table in VB via the OpenRecordset method
> fail with the error message "parse error near [name of the table]" or VB
> tells that it?s a connection error.
> That?s weird.
> MS Access has no problems connecting and writing to the database.
> VB?s Visual Database Manager can connect to the database, but can only
> read tables.
> MY VB programm can?t even connect to the tables, but it worked quite
> good via ODBC to the Access Database.
>
>
> I don?t know what i can anymore, so please help if you know a solution.
>
>
> Christoph Nelles
^ permalink raw reply [nested|flat] 27+ messages in thread
* RE: ODBC-Problem
@ 2001-01-03 16:05 Michael Davis <mdavis@sevainc.com>
0 siblings, 0 replies; 27+ messages in thread
From: Michael Davis @ 2001-01-03 16:05 UTC (permalink / raw)
To: 'Evil Azrael' <EvilAzrael@EvilAzrael.de>; pgsql-interfaces
This sounds strange. I can connect to many tables in less than a minute.
I can open tables in seconds regardless of how many rows are in the
tables. Access usually only selects 20-30 rows at a time. My ODBC
connections to PostgreSQL in Access are fast. Not as fast as opening local
Access tables by much faster than 1 minute. You can try different options
in your connect statement. Some options work with ODBC, others don't. If
this does not help, you will have to email me your VBA code.
-----Original Message-----
From: Evil Azrael [SMTP:EvilAzrael@EvilAzrael.de]
Sent: Wednesday, January 03, 2001 1:44 AM
To: mdavis@sevainc.com
Subject: Re: ODBC-Problem
thanx for the answer.
i have in every table a primary index called ID, but ODBC and VB don?t
accept it as a primary keys. and the performance of the OBDC connection
is rather bad. he needs almost 1 minute to connect to a table with 300k
rows, for just appending a few lines. even sql calls fails. i postponed
the whole transfer for a time and check it then again.
but thanx for the reply
Christoph Nelles
Michael Davis wrote:
>
> Add a primary key index to the tables that you want to be able to update.
> Access relies on the primary key for a lot of things. I recommend you
add
> a primary key to all postgres tables.
>
> -----Original Message-----
> From: Evil Azrael [SMTP:EvilAzrael@EvilAzrael.de]
> Sent: Sunday, December 31, 2000 8:50 PM
> To: pgsql-interfaces@postgresql.org
> Subject: ODBC-Problem
>
> HI
>
> I have just moved my old MS Access Database to a postgres database via
> odbc. all went okay, and i can access the database in MS Access via
> ODBC. Only a Client programm that i wrote can?t access the database
> anymore via ODBC. The Visual BAsic Database programm says that the
> database itself is updateable, but the tables in it aren?t updateable,
> and all tries to connect to a table in VB via the OpenRecordset method
> fail with the error message "parse error near [name of the table]" or VB
> tells that it?s a connection error.
> That?s weird.
> MS Access has no problems connecting and writing to the database.
> VB?s Visual Database Manager can connect to the database, but can only
> read tables.
> MY VB programm can?t even connect to the tables, but it worked quite
> good via ODBC to the Access Database.
>
> I don?t know what i can anymore, so please help if you know a solution.
>
> Christoph Nelles
^ permalink raw reply [nested|flat] 27+ messages in thread
* ODBC problem
@ 2001-06-07 08:07 Simon Emmanuel Rivas <simon-emmanuel.rivas@isr.thomson-csf.com>
0 siblings, 1 reply; 27+ messages in thread
From: Simon Emmanuel Rivas @ 2001-06-07 08:07 UTC (permalink / raw)
To: pgsql-interfaces
Hi!
I have a problem using the ODBC interface. The problem is quite simple:
I have created a table with only one field, as follows:
create table test (key numeric(1));
Very simple, right? The problem is that, when I look at this table
through a client program which runs under Windows (postgres runs under
Linux), the field "key" seems to be declared as numeric(3).
Does the problem come from ODBC or the client program?
Thanx for your help!
PS: the client program is Data Factory from Quest Software. I use
Postgres 7.1.1 and the ODBC driver is v7.01.0005.
^ permalink raw reply [nested|flat] 27+ messages in thread
* Re: ODBC problem
@ 2001-06-12 02:28 Hiroshi Inoue <Inoue@tpf.co.jp>
parent: Simon Emmanuel Rivas <simon-emmanuel.rivas@isr.thomson-csf.com>
0 siblings, 0 replies; 27+ messages in thread
From: Hiroshi Inoue @ 2001-06-12 02:28 UTC (permalink / raw)
To: Simon Emmanuel Rivas <simon-emmanuel.rivas@isr.thomson-csf.com>; +Cc: pgsql-interfaces
Simon Emmanuel Rivas wrote:
>
> Hi!
>
> I have a problem using the ODBC interface. The problem is quite simple:
> I have created a table with only one field, as follows:
> create table test (key numeric(1));
> Very simple, right? The problem is that, when I look at this table
> through a client program which runs under Windows (postgres runs under
> Linux), the field "key" seems to be declared as numeric(3).
> Does the problem come from ODBC or the client program?
The problem seems to come from the client program.
For example, M$ Access recognizes numeric(1).
regards,
Hiroshi Inoue
^ permalink raw reply [nested|flat] 27+ messages in thread
* ODBC Problem
@ 2001-07-17 23:58 jamzb@airnet.com.au
0 siblings, 0 replies; 27+ messages in thread
From: jamzb@airnet.com.au @ 2001-07-17 23:58 UTC (permalink / raw)
To: pgsql-interfaces
Greetings people,
Before I go nuts, I wonder if anyone has solved this problem
before; I have been using the ODBC driver for our Postgres server to
develop software in Visual Basic with great success until just recently.
Symptoms of the problem are that queries on some machines execute
correctly, but taking the same code and executing it on another machine
returns empty recordsets. I made sure all the drivers were the same and
that the latest MDAC 2.7 was installed on all machines.
On further investigation, I found that on the affected machines, queries
to tables with an index come back with an empty recordset.
Win2k Terminal Server SP2: okay - queries return data
WinXP Beta2: okay - queries return data
WinNT4 Server: only queries on some tables return data
Win2k Server SP2: only queries on some tables return data
I guess this must be something to do with the setup of the ODBC driver
on these machines, but I can't for the life of me find any difference in
settings. All the machines use identical connect strings.
I looked at the ODBC logs to find something that was failing and
couldn't really see any thing bad:
conn=35795448,
SQLDriverConnect(out)='DRIVER={PostGreSQL};DATABASE=bmf;SERVER=bm
f.some.domain;PORT=5432;UID=postgres;PWD=xxxxx;READONLY=0;PROTOCOL=6.4;F
A
KEOIDINDEX=0;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=0;CONNSETT
INGS='
conn=35795448, query='SELECT * FROM userservices WHERE printform=true
AND formpr
inted IS NULL'
[ fetched 1 rows ]
conn=35795448, SQLDisconnect
So it looked like the row I wanted was retrieved but the recordset still
remained empty :-(
I believe the server is running Postgres 7.0.3 :
[root@bmf bin]# ./psql -V
psql (PostgreSQL) 7.0.3
contains readline, history support
Portions Copyright (c) 1996-2000, PostgreSQL, Inc
Portions Copyright (c) 1996 Regents of the University of California
Read the file COPYRIGHT or use the command \copyright to see the
usage and distribution terms.
All machines are using the same ODBC driver version 6.5, PSQLODBC.DLL
4/2/2000
If anyone knows if there is a known problem with this combo please let
me know and I will have a case to get the admin to upgrade.
Cheers & TIA,
Jamz.
=-=-=-=-=-=-=-=-=-=-=-=-
"We should have laser guns!"
- Andrew Hill (Post Support Call)
Attachments:
smime.p7s (application/x-pkcs7-signature, 3.7K) download
^ permalink raw reply [nested|flat] 27+ messages in thread
* ODBC Problem
@ 2001-07-18 00:10 Jamz@AirNet.Com.AU
0 siblings, 1 reply; 27+ messages in thread
From: Jamz@AirNet.Com.AU @ 2001-07-18 00:10 UTC (permalink / raw)
To: pgsql-interfaces
Greetings people,
Before I go nuts, I wonder if anyone has solved this problem
before; I have been using the ODBC driver for our Postgres server to develop
software in Visual Basic with great success until just recently.
Symptoms of the problem are that queries on some machines execute correctly,
but taking the same code and executing it on another machine returns empty
recordsets. I made sure all the drivers were the same and that the latest
MDAC 2.7 was installed on all machines.
On further investigation, I found that on the affected machines, queries to
tables with an index come back with an empty recordset.
Win2k Terminal Server SP2: okay - queries return data
WinXP Beta2: okay - queries return data
WinNT4 Server: only queries on some tables return data
Win2k Server SP2: only queries on some tables return data
I guess this must be something to do with the setup of the ODBC driver on
these machines, but I can't for the life of me find any difference in
settings. All the machines use identical connect strings.
I looked at the ODBC logs to find something that was failing and couldn't
really see any thing bad:
conn=35795448,
SQLDriverConnect(out)='DRIVER={PostGreSQL};DATABASE=bmf;SERVER=bm
f.some.domain;PORT=5432;UID=postgres;PWD=xxxxx;READONLY=0;PROTOCOL=6.4;FA
KEOIDINDEX=0;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=0;CONNSETTINGS
='
conn=35795448, query='SELECT * FROM userservices WHERE printform=true AND
formpr
inted IS NULL'
[ fetched 1 rows ]
conn=35795448, SQLDisconnect
So it looked like the row I wanted was retrieved but the recordset still
remained empty :-(
I believe the server is running Postgres 7.0.3 :
[root@bmf bin]# ./psql -V
psql (PostgreSQL) 7.0.3
contains readline, history support
Portions Copyright (c) 1996-2000, PostgreSQL, Inc
Portions Copyright (c) 1996 Regents of the University of California
Read the file COPYRIGHT or use the command \copyright to see the
usage and distribution terms.
All machines are using the same ODBC driver version 6.5, PSQLODBC.DLL
4/2/2000
If anyone knows if there is a known problem with this combo please let me
know and I will have a case to get the admin to upgrade.
Cheers & TIA,
Jamz.
=-=-=-=-=-=-=-=-=-=-=-=-
"We should have laser guns!"
- Andrew Hill (Post Support Call)
^ permalink raw reply [nested|flat] 27+ messages in thread
* RE: ODBC Problem
@ 2001-07-18 08:58 Henshall, Stuart - WCP <SHenshall@westcountrypublications.co.uk>
0 siblings, 0 replies; 27+ messages in thread
From: Henshall, Stuart - WCP @ 2001-07-18 08:58 UTC (permalink / raw)
To: 'Jamz@AirNet.Com.AU' <Jamz@AirNet.Com.AU>; pgsql-interfaces
It may well be worth trying the latest version of the driver (Have a look at
http://odbc.postgresql.org , or
http://www.ca.postgresql.org/ftpsite/odbc/versions/full/)
Also there is an postgreSQL ODBC specific list: pgsql-odbc@postgresql.org
- Stuart
> -----Original Message-----
> From: Jamz@AirNet.Com.AU [SMTP:Jamz@AirNet.Com.AU]
> Sent: Wednesday, July 18, 2001 1:11 AM
> To: pgsql-interfaces@postgresql.org
> Subject: ODBC Problem
>
> Greetings people,
> Before I go nuts, I wonder if anyone has solved this problem
> before; I have been using the ODBC driver for our Postgres server to
> develop software in Visual Basic with great success until just recently.
>
> Symptoms of the problem are that queries on some machines execute
> correctly, but taking the same code and executing it on another machine
> returns empty recordsets. I made sure all the drivers were the same and
> that the latest MDAC 2.7 was installed on all machines.
>
> On further investigation, I found that on the affected machines, queries
> to tables with an index come back with an empty recordset.
>
> Win2k Terminal Server SP2: okay - queries return data
> WinXP Beta2: okay - queries return data
> WinNT4 Server: only queries on some tables return data
> Win2k Server SP2: only queries on some tables return data
>
> I guess this must be something to do with the setup of the ODBC driver on
> these machines, but I can't for the life of me find any difference in
> settings. All the machines use identical connect strings.
>
> I looked at the ODBC logs to find something that was failing and couldn't
> really see any thing bad:
>
> conn=35795448,
> SQLDriverConnect(out)='DRIVER={PostGreSQL};DATABASE=bmf;SERVER=bm
> f.some.domain;PORT=5432;UID=postgres;PWD=xxxxx;READONLY=0;PROTOCOL=6.4;FA
> KEOIDINDEX=0;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=0;CONNSETTIN
> GS='
> conn=35795448, query='SELECT * FROM userservices WHERE printform=true AND
> formpr
> inted IS NULL'
> [ fetched 1 rows ]
> conn=35795448, SQLDisconnect
>
> So it looked like the row I wanted was retrieved but the recordset still
> remained empty :-(
>
> I believe the server is running Postgres 7.0.3 :
>
> [root@bmf bin]# ./psql -V
> psql (PostgreSQL) 7.0.3
> contains readline, history support
> Portions Copyright (c) 1996-2000, PostgreSQL, Inc
> Portions Copyright (c) 1996 Regents of the University of California
> Read the file COPYRIGHT or use the command \copyright to see the
> usage and distribution terms.
>
> All machines are using the same ODBC driver version 6.5, PSQLODBC.DLL
> 4/2/2000
>
> If anyone knows if there is a known problem with this combo please let me
> know and I will have a case to get the admin to upgrade.
>
> Cheers & TIA,
> Jamz.
>
>
>
> =-=-=-=-=-=-=-=-=-=-=-=-
> "We should have laser guns!"
> - Andrew Hill (Post Support Call)
>
^ permalink raw reply [nested|flat] 27+ messages in thread
* RE: ODBC Problem
@ 2001-07-18 10:32 László Tibor <ltibor@mail.tiszanet.hu>
parent: Jamz@AirNet.Com.AU
0 siblings, 0 replies; 27+ messages in thread
From: László Tibor @ 2001-07-18 10:32 UTC (permalink / raw)
To: Jamz@AirNet.Com.AU; pgsql-interfaces
I had a same problem with Win98SE. Some of our datasets showed wrong empty
recordsets using C++Builder executable with ODBCExpress components and the
latest driver. But after installed a newer MDAC (2.5 I think) it
dissapeared. I didn't tried the latest MDAC.
So nothing useful for you :-(
Tibor Laszlo
ltibor@mail.tiszanet.hu
-----Original Message-----
From: pgsql-interfaces-owner@postgresql.org
[mailto:pgsql-interfaces-owner@postgresql.org]On Behalf Of
Jamz@AirNet.Com.AU
Sent: Wednesday, July 18, 2001 2:11 AM
To: pgsql-interfaces@postgresql.org
Subject: [INTERFACES] ODBC Problem
Greetings people,
Before I go nuts, I wonder if anyone has solved this problem
before; I have been using the ODBC driver for our Postgres server to develop
software in Visual Basic with great success until just recently.
Symptoms of the problem are that queries on some machines execute
correctly, but taking the same code and executing it on another machine
returns empty recordsets. I made sure all the drivers were the same and
that the latest MDAC 2.7 was installed on all machines.
On further investigation, I found that on the affected machines, queries
to tables with an index come back with an empty recordset.
Win2k Terminal Server SP2: okay - queries return data
WinXP Beta2: okay - queries return data
WinNT4 Server: only queries on some tables return data
Win2k Server SP2: only queries on some tables return data
I guess this must be something to do with the setup of the ODBC driver on
these machines, but I can't for the life of me find any difference in
settings. All the machines use identical connect strings.
I looked at the ODBC logs to find something that was failing and couldn't
really see any thing bad:
conn=35795448,
SQLDriverConnect(out)='DRIVER={PostGreSQL};DATABASE=bmf;SERVER=bm
f.some.domain;PORT=5432;UID=postgres;PWD=xxxxx;READONLY=0;PROTOCOL=6.4;FA
KEOIDINDEX=0;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=0;CONNSETTINGS
='
conn=35795448, query='SELECT * FROM userservices WHERE printform=true AND
formpr
inted IS NULL'
[ fetched 1 rows ]
conn=35795448, SQLDisconnect
So it looked like the row I wanted was retrieved but the recordset still
remained empty L
I believe the server is running Postgres 7.0.3 :
[root@bmf bin]# ./psql -V
psql (PostgreSQL) 7.0.3
contains readline, history support
Portions Copyright (c) 1996-2000, PostgreSQL, Inc
Portions Copyright (c) 1996 Regents of the University of California
Read the file COPYRIGHT or use the command \copyright to see the
usage and distribution terms.
All machines are using the same ODBC driver version 6.5, PSQLODBC.DLL
4/2/2000
If anyone knows if there is a known problem with this combo please let me
know and I will have a case to get the admin to upgrade.
Cheers & TIA,
Jamz.
=-=-=-=-=-=-=-=-=-=-=-=-
"We should have laser guns!"
- Andrew Hill (Post Support Call)
^ permalink raw reply [nested|flat] 27+ messages in thread
* RE: ODBC Problem
@ 2001-07-24 09:04 Henshall, Stuart - WCP <SHenshall@westcountrypublications.co.uk>
0 siblings, 0 replies; 27+ messages in thread
From: Henshall, Stuart - WCP @ 2001-07-24 09:04 UTC (permalink / raw)
To: 'jamzb@airnet.com.au' <jamzb@airnet.com.au>; pgsql-interfaces
Hello,
the PostgreSQL ODBC driver is up to 7.01.0006 now. Try this out. It
is available on odbc.postgresql.org. (It may also be worth looking at the
archives of the pgsql-odbc mailing list or on techdocs.postgresql.org).
- Stuart
> -----Original Message-----
> From: jamzb@airnet.com.au [SMTP:jamzb@airnet.com.au]
> Sent: Wednesday, July 18, 2001 12:58 AM
> To: pgsql-interfaces@postgresql.org
> Subject: ODBC Problem
>
> Greetings people,
> Before I go nuts, I wonder if anyone has solved this problem
> before; I have been using the ODBC driver for our Postgres server to
> develop software in Visual Basic with great success until just recently.
>
> Symptoms of the problem are that queries on some machines execute
> correctly, but taking the same code and executing it on another machine
> returns empty recordsets. I made sure all the drivers were the same and
> that the latest MDAC 2.7 was installed on all machines.
>
> On further investigation, I found that on the affected machines, queries
> to tables with an index come back with an empty recordset.
>
> Win2k Terminal Server SP2: okay - queries return data
> WinXP Beta2: okay - queries return data
> WinNT4 Server: only queries on some tables return data
> Win2k Server SP2: only queries on some tables return data
>
> I guess this must be something to do with the setup of the ODBC driver on
> these machines, but I can't for the life of me find any difference in
> settings. All the machines use identical connect strings.
>
> I looked at the ODBC logs to find something that was failing and couldn't
> really see any thing bad:
>
> conn=35795448,
> SQLDriverConnect(out)='DRIVER={PostGreSQL};DATABASE=bmf;SERVER=bm
> f.some.domain;PORT=5432;UID=postgres;PWD=xxxxx;READONLY=0;PROTOCOL=6.4;FA
> KEOIDINDEX=0;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=0;CONNSETTIN
> GS='
> conn=35795448, query='SELECT * FROM userservices WHERE printform=true AND
> formpr
> inted IS NULL'
> [ fetched 1 rows ]
> conn=35795448, SQLDisconnect
>
> So it looked like the row I wanted was retrieved but the recordset still
> remained empty :-(
>
> I believe the server is running Postgres 7.0.3 :
>
> [root@bmf bin]# ./psql -V
> psql (PostgreSQL) 7.0.3
> contains readline, history support
> Portions Copyright (c) 1996-2000, PostgreSQL, Inc
> Portions Copyright (c) 1996 Regents of the University of California
> Read the file COPYRIGHT or use the command \copyright to see the
> usage and distribution terms.
>
> All machines are using the same ODBC driver version 6.5, PSQLODBC.DLL
> 4/2/2000
>
> If anyone knows if there is a known problem with this combo please let me
> know and I will have a case to get the admin to upgrade.
>
> Cheers & TIA,
> Jamz.
>
>
>
> =-=-=-=-=-=-=-=-=-=-=-=-
> "We should have laser guns!"
> - Andrew Hill (Post Support Call)
>
^ permalink raw reply [nested|flat] 27+ messages in thread
end of thread, other threads:[~2001-07-24 09:04 UTC | newest]
Thread overview: 27+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1998-07-09 17:50 ODBC Problem Len Morgan <len-morgan@xroadstx.com>
1998-07-10 16:03 ` Byron Nikolaidis <byronn@insightdist.com>
1998-07-21 22:19 ` Byron Nikolaidis <byronn@insightdist.com>
1999-07-15 05:21 ODBC problem Terence Chan <kin.chan@technologist.com>
1999-07-15 06:14 ` Re: [INTERFACES] ODBC problem Hannu Krosing <hannu@trust.ee>
1999-07-15 06:22 ` RE: [INTERFACES] ODBC problem Terence Chan <kin.chan@technologist.com>
1999-07-15 13:49 [Fwd: [INTERFACES] ODBC problem] Byron Nikolaidis <byronn@solipsys.com>
2000-04-02 07:57 ODBC Problem Albert J. Insogna <ainsogna@hotmail.com>
2000-04-02 15:37 ` Thomas Lockhart <lockhart@alumni.caltech.edu>
2000-10-07 09:02 ODBC problem George P. Esperanza <george@calamba.laguna.net>
2000-10-07 14:31 ` Re: ODBC problem Cedar Cox <cedarc@visionforisrael.com>
2000-10-08 23:53 ` Re: ODBC problem Tom Samplonius <tom@sdf.com>
2000-10-09 16:32 ` Re: ODBC problem Peter Eisentraut <peter_e@gmx.net>
2000-10-09 16:45 ` Re: ODBC problem Tom Lane <tgl@sss.pgh.pa.us>
2000-10-09 09:52 ODBC problem soulimane sabir <sabirsou@caramail.com>
2001-01-01 03:49 ODBC-Problem Evil Azrael <EvilAzrael@EvilAzrael.de>
2001-01-01 13:01 ` Re: ODBC-Problem Evil Azrael <EvilAzrael@EvilAzrael.de>
2001-01-03 00:54 RE: ODBC-Problem Michael Davis <mdavis@sevainc.com>
2001-01-03 14:01 ` Re: RE: ODBC-Problem Adam Lang <aalang@rutgersinsurance.com>
2001-01-03 16:05 RE: ODBC-Problem Michael Davis <mdavis@sevainc.com>
2001-06-07 08:07 ODBC problem Simon Emmanuel Rivas <simon-emmanuel.rivas@isr.thomson-csf.com>
2001-06-12 02:28 ` Re: ODBC problem Hiroshi Inoue <Inoue@tpf.co.jp>
2001-07-17 23:58 ODBC Problem jamzb@airnet.com.au
2001-07-18 00:10 ODBC Problem Jamz@AirNet.Com.AU
2001-07-18 10:32 ` László Tibor <ltibor@mail.tiszanet.hu>
2001-07-18 08:58 RE: ODBC Problem Henshall, Stuart - WCP <SHenshall@westcountrypublications.co.uk>
2001-07-24 09:04 RE: ODBC Problem Henshall, Stuart - WCP <SHenshall@westcountrypublications.co.uk>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox