Re: FW: psqlodbc X OpenOffice solution for adding records

Please try the snapshot(7.03.0102) dll at
http://www.geocities.jp/inocchichichi/psqlodbc/ .

regards,
Hiroshi Inoue

> -----Original Message-----
> From: pgsql-odbc-owner(at)postgresql(dot)org
> [mailto:pgsql-odbc-owner(at)postgresql(dot)org]On Behalf Of Dave Page
> Sent: Friday, May 16, 2003 5:11 PM
> To: pgsql-odbc(at)postgresql(dot)org
> Cc: Suportetc
> Subject: [ODBC] FW: psqlodbc X OpenOffice solution for adding records
>
>
> [Forwarded to the ODBC support list]
>
> > --- Suportetc <suportetc(at)redemeta(dot)com(dot)br> wrote:
> > > Date: Thu, 15 May 2003 13:36:09 -0000
> > > From: Suportetc <suportetc(at)redemeta(dot)com(dot)br>
> > > To: <xgbe(at)yahoo(dot)com>
> > > CC: <dg(at)openoffice(dot)org>, <fs(at)openoffice(dot)org>
> > > Subject: psqlodbc X OpenOffice solution for adding records
> > >
> > > Hello, sir:
> > > I was struggling with strange problems regarding
> > OpenOffice 1.0.3 and
> > > psqlodbc.
> > > first, it was impossible to connect OO to psql.
> > > Then reading OO site, a note telling about DOWNGRADING psqlodbc
> > > driver to
> > > 7_02_003.
> > >
> > > Second, it was impossible to add new records.
> > > Sw complains about some cursor problem and that it cannot insert
> > > duplicate records with same primary key.
> > > Reading OO docs, and db bug issues at site, they told it is because
> > > some
> > > odbc 3.0 calls not completely implemented at psqlodbc, I realized.
> > > MySQL odbc driver works well.
> > > StarOffice 5.2 works well (uses odbc 2.0).
> > > By reading your FAQ, I realize that selecting " use Declare/Fetch"
> > > could
> > > affect cursor problems.
> > >
> > > Voila.
> > >
> > > I am not sure about it solving autoincrement fields. Testing is
> > > needed.
> > >
> > > Please, write a note about this at your FAQ and contact OpenOffice
> > > crew to writing it also.
> > > This could help many postgresql users.
> > > Regards.
> > > Andre Felipe Machado
> > > http://www.techforce.com.br
> > > messages not answered in 2 bussiness days were lost. Please send
> > > again.