From: | "Dave Held" <dave(dot)held(at)arraysg(dot)com> |
---|---|
To: | <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: ODBC Drivers |
Date: | 2006-04-12 22:18:41 |
Message-ID: | 49E94D0CFCD4DB43AFBA928DDD20C8F902678B8A@asg002.asg.local |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
> -----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).
Dave
From | Date | Subject | |
---|---|---|---|
Next Message | Ludek Finstrle | 2006-04-13 06:06:21 | Re: ODBC Drivers |
Previous Message | Dave Page | 2006-04-12 22:13:44 | Re: ODBC Drivers |