>>>Hi,
>>>
>>>This is a follow up my thread on the same subject. Just to refresh:
>>>I store (un-encrypted) a string that consists of "Y" and "N" in a 250 char field GRP_ACCESS (in SQL Server). Each position corresponds to a feature in the application. When a user logs in, based on his credentials, he may or may not have access to a feature (based on the value in the GRP_ACCESS field).
>>>
>>>I tried to encrypt the values in this field using the function cipher() (created by S. Berezniker). This function creates an encrypted string (based on the "YYYYNNNNYN..." But if one were to look at the encrypted field you can clearly see a pattern. For example, the users who have/had all "Y"s in the un-encrypted field get the same encrypted string. It is just the encrypted string has many non-ascii characters; so it looks unreadable. But if someone wants to, they can simply store the field value into a variable and then execute the UPDATE table and set this value in all records. I doubt my customer would do it. But, I would like to explore other ways to encrypt the field.
>>>
>>>If you have any suggestions, please let me know.
>>
>>Use integer field instead.
>>http://www.atoutfox.org/articles.asp?ACTION=FCONSULTER&ID=0000000348
>
>A quick read of the article (and it amazes me that after 5 year of learning French, I can read fairly well). Anyway, I do have this type of code in my app when I need no more than 32 choices. Your code offers the same. But in my case (for this string) I need 250 choices. I thought about applying the same routine and breaking the 250 into several Int fields. But, so far, I am not convinced that this would be a good choice for me.
>Thank you for suggesting it.

It was worth a shot.