Thread: ODBC Drivers

ODBC Drivers

From
"Dave Held"
Date:

Is there a complete list of Postgres ODBC drivers somewhere?  I need
a good, reliable, highly conforming driver or my boss is going to make us
switch to SQL Server.  Unfortunately, the current driver seems to fail the
"highly conforming" criterion as far as Crystal Reports is concerned.  I
don't want to use the experimental driver in CVS because I have a
production environment that needs to be stable.  I wanted to try the
Command Prompt driver, but they don't even list it under the Products
section of their site, presumably because they are still working on it?
Any references to other drivers, commercial or not, would be greatly
appreciated (though my cursory search seems to indicate that the field
is pretty narrow).

__
David B. Held
Software Engineer/Array Services Group
200 14th Ave. East,  Sartell, MN 56377
320.534.3637 320.253.7800 800.752.8129

Re: ODBC Drivers

From
"Dave Page"
Date:
-----Original Message-----
From: "Dave Held"<dave.held@arraysg.com>
Sent: 12/04/06 23:08:19
To: "pgsql-odbc@postgresql.org"<pgsql-odbc@postgresql.org>
Subject: [ODBC] ODBC Drivers

> Unfortunately, the current driver seems to fail the
> "highly conforming" criterion as far as Crystal Reports is concerned.

In what way? We've been using psqlODBC with Crystal 7, 8 & now 11 since pg 6.4ish with no problems.

Regards, Dave

-----Unmodified Original Message-----
> Is there a complete list of Postgres ODBC drivers somewhere?  I need
> a good, reliable, highly conforming driver or my boss is going to make us
> switch to SQL Server.  Unfortunately, the current driver seems to fail the
> "highly conforming" criterion as far as Crystal Reports is concerned.  I
> don't want to use the experimental driver in CVS because I have a
> production environment that needs to be stable.  I wanted to try the
> Command Prompt driver, but they don't even list it under the Products
> section of their site, presumably because they are still working on it?
> Any references to other drivers, commercial or not, would be greatly
> appreciated (though my cursory search seems to indicate that the field
> is pretty narrow).
>
> __
> David B. Held
> Software Engineer/Array Services Group
> 200 14th Ave. East,  Sartell, MN 56377
> 320.534.3637 320.253.7800 800.752.8129
>
>

Re: ODBC Drivers

From
"Dave Held"
Date:
> -----Original Message-----
> From: Dave Page [mailto:dpage@vale-housing.co.uk]
> Sent: Wednesday, April 12, 2006 5:14 PM
> To: Dave Held; pgsql-odbc@postgresql.org
> Subject: RE: [ODBC] ODBC Drivers
> 
> [Me]
> > Unfortunately, the current driver seems to fail the
> > "highly conforming" criterion as far as Crystal Reports
> > is concerned.  
> 
> In what way? We've been using psqlODBC with Crystal 7, 8 & 
> now 11 since pg 6.4ish with no problems.

Heh.  Just my luck.  In Crystal 10, against an 8.0 db, and
through a Business Objects XI Business View, any varchar with
length > 255 shows up as a goofy data type (Persistent.memo
if I recall correctly).  Unfortunately, Crystal won't even
acknowledge the existence of these fields, so you can't even
put them on your report.  SQL Server does just fine with large
varchars.  It would be even nicer to just use text fields, but
those confuse Crystal even more (usually it displays a length
of -1 and does weird things).

Dave

Re: ODBC Drivers

From
Ludek Finstrle
Date:
> > "highly conforming" criterion as far as Crystal Reports is concerned.  I
> > don't want to use the experimental driver in CVS because I have a
> > production environment that needs to be stable.  I wanted to try the

I think the Experimental Enhanced Branch (psqlODBC 07.03.026X - which
is now the CVS Head) is more stable than 08.01.0200 (which is marked as
stable). Feel free to test it.

I see no motivation to support 08.01 becouse it's dead end.

> > Any references to other drivers, commercial or not, would be greatly
> > appreciated (though my cursory search seems to indicate that the field
> > is pretty narrow).

What about google with: postgresql odbc driver?

Regards,

Luf

Re: ODBC Drivers

From
"Dave Page"
Date:

> -----Original Message-----
> From: pgsql-odbc-owner@postgresql.org
> [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Dave Held
> Sent: 12 April 2006 23:19
> To: pgsql-odbc@postgresql.org
> Subject: Re: [ODBC] ODBC Drivers
>
> > -----Original Message-----
> > From: Dave Page [mailto:dpage@vale-housing.co.uk]
> > Sent: Wednesday, April 12, 2006 5:14 PM
> > To: Dave Held; pgsql-odbc@postgresql.org
> > Subject: RE: [ODBC] ODBC Drivers
> >
> > [Me]
> > > Unfortunately, the current driver seems to fail the "highly
> > > conforming" criterion as far as Crystal Reports is concerned.
> >
> > In what way? We've been using psqlODBC with Crystal 7, 8 & now 11
> > since pg 6.4ish with no problems.
>
> Heh.  Just my luck.  In Crystal 10, against an 8.0 db, and
> through a Business Objects XI Business View, any varchar with
> length > 255 shows up as a goofy data type (Persistent.memo
> if I recall correctly).  Unfortunately, Crystal won't even
> acknowledge the existence of these fields, so you can't even
> put them on your report.  SQL Server does just fine with
> large varchars.  It would be even nicer to just use text
> fields, but those confuse Crystal even more (usually it
> displays a length of -1 and does weird things).

Hmm, we never use varchars that big but use text instead with no
problems. We don't use Business Objects XI Business Views though.

Have you tried tweaking the MaxVarchar setting in your DSN? That
defaults to 254...

Regards, Dave