Could you point what must be configured on a DBF file to correctly save an encripted string?
Hi Experts
I'm using vfpencryption71.fll that perfectly runs and correctly saves on a not indexed DBF file.
But if I use an indexed DBF file (I don't know if it's really the cause, this occurs:
The DBF index configuration Collate is Machine.
The codepage of the not indexed table and the indexed table is the same 1252.
The problem arises on CDX not in IDX.
Thanks in advance.
I'm using vfpencryption71.fll that perfectly runs and correctly saves on a not indexed DBF file.
But if I use an indexed DBF file (I don't know if it's really the cause, this occurs:
*-- The string that must be saved
OµÆp%D½×°W“˜Âá?ËR•(óÏ Sqϧux¹
*-- The string saved
Oü-+p%D+×°W"˜Âá?ËR•(óI SqI§ux1
The DBF index configuration Collate is Machine.
The codepage of the not indexed table and the indexed table is the same 1252.
The problem arises on CDX not in IDX.
Thanks in advance.
Who is Participating?
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
All Courses
From novice to tech pro — start learning today.
Important is also the CP used in the application - see CPCURRENT() function.
Or you may define the column with NOCPTRAN keyword - visible as Character (binary) or Memo (binary) in Table designer. In such case the CP conversion is suppressed.
Optionally the varbinary column could be used. This data type also does not allow the conversion.
To convert text into binary data type simply write 0h + "text". Or 0h + variable etc. I would guess the automatic data type conversion works well here.
The string example in your question was converted from CP 1252 to CP 437 or some other MS DOS CP or to a CP which does not support upper index characters like ¹ ² ³.