Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The validation pattern can be any OI pattern acceptable to the built-in OI function IConv. If you wish to remove a pattern, set this field to "None". Also, all user defined patterns must be incased written in ALL CAPS and encased in square brackets, e.g., "[PHONE_FORMAT]"

...

The conversion pattern must be a custom conversion. Simply passing built-in conversions does not work due to technical limitations. The SRP EditTable Controls calls the FMT routine via RevCAPI, and for reasons unknown to us, built-in conversions do not work when called from outside BASIC+. However, custom conversions--conversion within square brackets--work just fine. As with Validation Patterns, these must be written in ALL CAPS and encased in square brackets. We recommend creating a custom converter that is a simple wrapper around OConv. For example:

Code Block
Compile subroutine Cell_Conv(Conv, Ans, Branch, ReturnData)

 IfIf Conv EQ "OCONV" then
   If Branch[1, 1] EQ "D" then
       If Num(Ans) then
           // The data is already in internal format, so just OConv it
           ReturnData = OConv(Ans, Branch)
       end else
           // The data is an some date format, so IConv it first, then OConv it
           ReturnData = OConv(IConv(Ans, "D"), Branch)
       end
   end else
       // For all non-date types, IConv first (just in case), then OConv it
       ReturnData = OConv(IConv(Ans, Branch), Branch)
   end
end else
   // IConv as usual
   ReturnData = IConv(Ans, Branch)
end

Return

...