Development has found this to be a problem with how the compiler recognizes the Boolean type within the evaluate statement and the problem has now been addressed in our next major product release VC 3.0 which will be delivered later this year. If you could open up a support incident with Customer Care and include my name in the description then I will add the incident to the problem report so that you will be notified when the fix is available. The workaround right now would be to break up the statement like you demonstrate and use only a data-item defined as a condition-value or a System.Boolean (full namespace) as the subject of the evaluate. The alternative is to use an if statement which can handle the full expression without a problem. if txtEmailAddress::Text::IsValidEmail() *>some code else *>some code end-if
↧