1) The solution offered is commensurate with the answers to the 3 questions I initially asked him, specifically casual user + low value.
2) Neither method, mine or the replacing of D with E, is encryption. It is just encoding. Encryption requires a key + encryption algorithm.
3) STRCONV() effectively does an extensive letter substitution and doing it a second time will throw off the casual user (assuming a casual user even knows what BASE64 encoding is).
4) It is fast and no coding required.
>Downside there may be the increased size of the resulting string. And it's not really encrypted - just encoded.
>TBH, as a programmed looking at the encoded string probably the first thing I try would be base64 decoding.
>Simple 'letter substitution' might be enough - though maybe with a more random mapping than I suggested?
>
>
>>tstring = "abc123xyz"
>>
>>tencrypted = STRCONV( STRCONV( m.tstring ,13 ) , 13 ) && double base64 encoded
>>
>>tdecrypted = STRCONV( STRCONV( m.tencrypted ,14 ) , 14 ) && double base64 decoded
>>
>>
>>>Jos
>>>
>>>I don't want to use complex third party encription tools
>>>
>>>I was just wondering if someone could be able to guess and revert the letters in the blob field
>>>even if invert many letters and numbers. (without having to source code I used to encrypt the field)
>>>
>>>Moises
>>>
>>>
>>>
>>>>Moises,
>>>>
>>>>1) From who are you trying to protect this information? Casual users or more experienced attacker?
>>>
>>>Casual users
>>>
>>>
>>>>2) What is the value of the information if it is stolen / compromised? High or low?
>>>
>>>Low
>>>
>>>>3) For how long is the information valuable i.e. for how long must it be protected?
>>>
>>>
>>>Long time
In the End, we will remember not the words of our enemies, but the silence of our friends - Martin Luther King, Jr.