Dan Yaeger
2021-05-24 21:21:47 UTC
Jeffrey
Bytes 1 & 2 are the offsets in the DBV where the data resides
Bytes 3 & 4 are the length of the stored data
Bytes 5 & 6 I don't know, at a guess the type of data stored
ie object, array, plain text, encryption type
The above is from memory so 1-4 may be reversed<g>
--
HTH
Steve Quinn
Never take life seriously. Nobody gets out alive anyway.
Sex is like air; it's not important unless you aren't getting any.
Health is merely the slowest possible rate at which one can die.
I am trying to figure out this same task on an old flexfile stored memo field. I am about to give up on this conversion and notify my users they will be transferring this data by hand.Bytes 1 & 2 are the offsets in the DBV where the data resides
Bytes 3 & 4 are the length of the stored data
Bytes 5 & 6 I don't know, at a guess the type of data stored
ie object, array, plain text, encryption type
The above is from memory so 1-4 may be reversed<g>
--
HTH
Steve Quinn
Never take life seriously. Nobody gets out alive anyway.
Sex is like air; it's not important unless you aren't getting any.
Health is merely the slowest possible rate at which one can die.
I cannot seem to get dClip to work for my memo fields (dbv), i just receive the pointer field with 6 characters. Almost every link on the internet is broken that references tools and materials to aid in this conversion.
Steve you seem to have a wealth of knowledge in these older clipper/flexfile systems. Do you know if the tool DBF/DBV -> DBF/DBT converter still exists? or if there are any resources that could get this data out? I am migrating everything to a MySQL database, i have all my dbf data already migrated, but the memo field has been the sticking point.
-Dan