Scott Marlowe <smarlowe@g2switchworks.com> wrote on 01/12/2005 01:36:34 PM:
> On Wed, 2005-01-12 at 15:28, MargaretGillon@chromalloy.com wrote:
> > Scott Marlowe <smarlowe@g2switchworks.com> wrote on 01/12/2005 01:06:30
PM:
> >
> > > On Wed, 2005-01-12 at 14:59, MargaretGillon@chromalloy.com wrote:
> > > > I am using ODBC to move Visual FoxPro7 tables (windows 2000 client)
> > into
> > > > Postgresql 7.x on a Redhat Linux server. All is working well except
for
> > > > Memo fields, which are Text fields in PostgreSql. I query the
> > Postgresql
> > > > table and get a cursor, update the cursor with the data, and send
it
> > back.
> > > > The contents of the memo field never make it back to the Postgresql
> > text
> > > > field. Other changes to the record's fields are saved with no
problem.
> > > >
> > > > At this time all my UI's have to be written in VFP. Is there a work
> > around
> > > > for this or am I going to have to eliminate Text/Memo fields from
my
> > > > tables?
> > >
> > > Postgresql doesn't support updatable cursors.
> >
> > The updateable cursors are inside the FoxPro software. By using them I
> > always get the table's current structure to build a UI on. Foxpro has
an
> > UpdateTable command that is used with the cursor. The command sends the
> > data back with updates and inserts via ODBC. I have been doing this for
a
> > month now, and it's going fine, but today is the first time I tried to
> > include data in the TEXT field.
>
>
> Ahh, ok. Misunderstood what your method was.
>
> Is there a setting in your ODBC driver for memo as text or something
> like that? It's been a while since I played with pgsql from a windows /
> odbc box, so I am a bit rusty here. It's just a wild guess.
On my Windows box the Postgresql ODBC driver is set with TEXT AS
LongVarChar, with a maximum length of 8190. FoxPro then turns the
LongVarChar into a Memo.
Margaret Gillon, IS Dept., Chromalloy Los Angeles, ext. 297