You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using dbf and creating new tables for vfp and then pushing data into those newly created tables.
When I use vfp to look at the memo fields they look like there should be some data but when viewing them they are empty.
Normally an empty memo field has memo in lower case but these are Memo so that means there is data there but clicking it returns nothing.
If I switch it to db3 when I create those same tables the memo fields are fine viewing in vfp.
Now viewing them thru python the memo fields do have data so not sure why vfp table memo fields don't work but the db3 table memo fields do. I am using vfp 9 not 6 I wouldn't think that is it but I don't know that for a fact.
The text was updated successfully, but these errors were encountered:
I am working with vfp 9 and still having this issue. I set the dbf_type='vfp' and it creates an .fpt file that doesn't seem to link properly and display the memo. If I leave off the dbf type it will create a .dbt file that does work correctly, but I need it to be fpt and support those datatypes. Is this still an active issue or is there a fix?
I am using dbf and creating new tables for vfp and then pushing data into those newly created tables.
When I use vfp to look at the memo fields they look like there should be some data but when viewing them they are empty.
Normally an empty memo field has memo in lower case but these are Memo so that means there is data there but clicking it returns nothing.
If I switch it to db3 when I create those same tables the memo fields are fine viewing in vfp.
Now viewing them thru python the memo fields do have data so not sure why vfp table memo fields don't work but the db3 table memo fields do. I am using vfp 9 not 6 I wouldn't think that is it but I don't know that for a fact.
The text was updated successfully, but these errors were encountered: