You're welcome. In fact this is exactly what binary data is meant for, one bit for every on/off option.

NB! I guess you have noticed that there is a corresponding Bitset() function, which makes it possible to set the bits individually? Plus a few other related Bitxxxx() functions.

>This suggestion has been incredibly helpful. Now instead of using X number of fields I can use just ONE field!
>Thank you again!
>
>>Why not use binary values?
>>
>>Choice 1 ---- 1
>>Choice 2 ---- 2
>>Choice 3 ---- 4
>>Choice 4 ---- 8
>>Choice 5 ---- 16
>>Choice 6 ---- 32
>>
>>Sum the values to store them. You can then easily retrieve which choices were selected.
>>
>>lnX = the sum
>>
>>To check if Choice 1 was selected : ?Bittest(lnX,0)
>>To check if Choice 2 was selected : ?Bittest(lnX,1)
>>To check if Choice 3 was selected : ?Bittest(lnX,2)
>>Note that the value after lnX is one lower than expected, since Bittest() is zero based.
>>
>>>Hi,
>>>
>>>I am looking for a formula (if possible) to convert a multiple choice(s) into a number. Kind of like the VFP Anchor property bit value works. Here is my example:
>>>Choice 1 ---- ##
>>>Choice 2 ---- ##
>>>Choice 3 ---- ##
>>>Choice 4 ---- ##
>>>Choice 5 ---- ##
>>>Choice 6 ---- ##
>>>
>>>Each choice above would have a number (##). Then when a user checks any number of choices (from 1 to 6), the "total" number is calculated. This "total" number should be unique for any combination of the selected choices. So that this number can be used (in reverse) to see what choices it represent.
>>>Any suggestions?