Passing type1 to type2 for parameter could give unexpected results
You've passed one of the following, which could cause unexpected results when examining the variable after the call:
- d or d. to a MISMATCH alpha not marked as IN
- string to unspecified alpha
- n or n. to d, d., or boolean without conversion
- d to d.
Possible solutions for the alpha issues are as follows:
- Change the parameter to IN.
- Explicitly set ^A around the decimal being passed on the call. For example,
If you want to turn off the warning for the string to unspecified alpha issue, you can use regular casting (i.e., (a)).
See Synergex KnowledgeBase article 100002319 for information about best practices for passing arguments, including techniques for resolving these warnings. In traditional Synergy, you will only get this error when using the -qnet (or /NET) compiler option. (Warning level 3 in Synergy .NET, warning level 4 in traditional Synergy)