> -----Original Message-----
> From: pgsql-odbc-owner(at)postgresql(dot)org
> [mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Dave Held
> Sent: 12 April 2006 23:19
> To: pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] ODBC Drivers
> > -----Original Message-----
> > From: Dave Page [mailto:dpage(at)vale-housing(dot)co(dot)uk]
> > Sent: Wednesday, April 12, 2006 5:14 PM
> > To: Dave Held; pgsql-odbc(at)postgresql(dot)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...
pgsql-odbc by date
|Next:||From: Dave Page||Date: 2006-04-13 07:54:06|
|Subject: CVS-tip; SSLmode & Kerberos|
|Previous:||From: Ludek Finstrle||Date: 2006-04-13 06:06:21|
|Subject: Re: ODBC Drivers|