The second post accomplished the same thing by making a copy of the Property Data Format assigned to the text property and, in the copy, adding %%u in the Prefix field, and then assigning the new Property Data Format to the property in the Property Set Definition. When adding that property to a Schedule Table Style, the original, non-underlined Property Data Format would be used. The benefit of this method is that you do not need to make any changes to the view block used by the Schedule Tag's Multi-View Block Definition.
This all worked fine back in 2005/2006 when the articles were written, and for some time thereafter. I have not checked, but I suspect that the addition of multi-line attribute support for Multi-View Blocks (and, therefore, in Schedule Tags) in the 2009 release broke the recognition of %%u as a code to indicate starting (and stopping) an underlining of text. It certainly does not work in the 2016 release.
Fortunately, there is still a way to do this, and it can be used with either method. Just substitute \\L [the MText underline code] for %%u. For example, given a text property called Name, you could create a formula property that creates an underlined version of that property by using the formula
RESULT = "\\L" & "[Name]"where "[Name]" is a properly created reference to the Name property.
Or, you could make a copy of the Property Data Format, such as Case - Upper, rename the copy Case - Upper - Underline, and add \\L to the Prefix property on the Formatting tab.