Josué Maldonado <josue@lamundial.hn> wrote on 01/12/2005 01:14:39 PM:
> Hello,
>
> El 12/01/2005 2:59 PM, MargaretGillon@chromalloy.com en su mensaje
escribio:
> > 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.
>
> Are you using SPT or remote views?
>
> > 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?
>
> I use VFP8 against Postgresql with ODBC without any issue with the memo
> fields.
>
>
> --
> Sinceramente,
> Josué Maldonado.
>
> "La TV es muy educativa. Cuando está encendida, me voy a otra habitación
> y me pongo a leer un libro." --Groucho Marx.
Hi Josué ,
I am using updatable cursors. I set up the cursor and set the cursor
properties to updateable and set the key field property so it knows the key
on the Postgresql table. The cursors are managed by a VFP class written by
a programmer named Andy Kramek. He uses this class to manage updateable
cursors in UI's for Oracle databases, I think on Unix servers. I have also
used the class to talk to an SQLServer on Windows2000.
The advantage with cursors is that I can pull down a set of 100-200
records, edit them, and send them back to the server and only one round
trip has occured. Saves a lot of time when loading new tables, which is
what I'm doing currently.
I looked in the archives and there are messages about this problem but the
fix for it was in the PGAdmin software. I didn't see anything that talked
about the same problem / fix for ODBC.
Regards,
Margaret Gillon, IS Dept., Chromalloy Los Angeles, ext. 297
