"Or should I just be taking a different approach to this problem..."
Those listed 'steps' and also the listed 'projects' should be records in a related table. This question is only the beginning indicator of problems with using a single field.
However, to get the last value in a checkbox, create a calculation (result is text) with:
Substitute ( RightValues ( text ; 1 ) ; ¶ ; "" )
You are absolutely right now that I think about it. I am a newbee at this and the first thought was checkboxes but it makes much more sense to use related tables in this case. Thanks for the advise...
Another calculation that returns the last item clicked in the field is:
GetValue ( text ; valueCount ( text ) )
Both calculations return the last value clicked by the user's mouse--not the lowest selected checkbox in the checkbox field's list of values--just to be clear on what you'll get here.
LOL, I kept feeling there was something very simple that I was forgetting! Ever have that happen, Phil? Thanks for the catch! Using xValues leaves a blank line at the end while GetValue() can be specific.
All the time and you have pointed some of them out from time to time, which I appreciate.
That extra return from the Leftwords, rightwords and middlewords is a "feature" that I find most irritating. When I figured out Getvalue could be used to replace 90% of what I was using the other functions to accomplish, I was quite pleased to make that change in my own coding.
"All the time...
That extra return from the Leftwords, rightwords and middlewords..."
This is one of those times ;-)