Yes, that's correct.
I was using linked tables to Access and when my psql db ended up with
fields longer than 255 it gave me error on that line.
Also, prior to converting my Access db using pgAdmin it wouldn't work
so I had to enter my Access db and cut down on fields exceeding 255.
Regards,
Aage
"W. van den Akker" wrote:
>
> Initally I've done that too, but I have to convert several databases.
>
> PostgreSQL does support longvar fields for string longer that 255, does it??
>
> Willem
>
> ----- Original Message -----
> From: Aage J. Skjolingstad <aages@aajs.com>
> To: W. van den Akker <wvdakker@wilsoft.nl>
> Sent: Saturday, March 04, 2000 10:12 AM
> Subject: Re: [INTERFACES] ODBC
>
> > Hi,
> >
> > I had a similar problem and chose to change all my capital letters to
> > lower case prior to converting from Access, ---- It finally made my
> > life easier after doing so.
> > (and field sizes max 255)
> >
> > Good Luck
> >
> > Aage
> >
> > > "W. van den Akker" wrote:
> > >
> > > Hi,
> > >
> > > I've some (only one actually) problems with the conversion
> > > from Access to PostgreSQL. The table and columnnames
> > > of the Access database do have sometimes capitals (ThisTable,
> > > ThisColumn).
> > > If I convert this table or row, the table and row are created but I
> > > cann't
> > > access them. It lookes like the postgress engine converts
> > > automaticly all
> > > names to lowercase. If a table is created the conversion to
> > > lowercases
> > > doesn't occur.
> > >
> > > Am I doing something wrong, or need the postgress ODBC-driver be
> > > changed?
> > >
> > > TIA
> > >
> > > Willem
> >
