|
I have to withdraw the value of a memo field in my app, and then insert that value in another record. In certain records, the info that i withdraw ir corrupt. It contains the real data of the memo field, and then a \u001a character followed by scrambled info of another recognizable (but no existence justificable) memo fields in the table. How can i obtain correctly the info of all my memo fields?
|
|
Yeah. A normal DBT memo data should end with 0x1a 0x1a flag, but it seems that some data is abnormal with only one 0x1a flag. What's the original data source for invalid memo data? You can use indexOf('\u001a') and substring to fix those data.
|
I've already used that solution (indexOf). And works well, but my question was about avoiding this method, maybe changing some property or configuration of the library.
As I told you, i have to "move" the info from a table to another, to later modify that info in the second table. I'm afraid that if the library detects only de "0x1a 0x1a" flag and not the "0x1a" flag, my data would become corrupt, because the data to be written have to be modified by a clipper app.
May I'd be worried about it? or it does not cause any additional troubles?
|
>I'm afraid that if the library detects only de "0x1a 0x1a" flag and not the "0x1a" flag
Yeah because Only 0x1a 0x1a flag is normal.
If your data is modified by Clipper application at the same time, you should use lockType=CLIPPER to avoid the possible 0x1a.
|
Main
webmaster@hxtt.com