This macro compiler warning means that the compiled code of the present macro needed to be spliced due to a bug of the new macro compiler when combining in the same code line the call a user-defined function added to a string or an integer.

 

The splice should have fixed the compiled code, but if you encounter strange behavior, then you can use either of the solutions below.

 

Solution 1

 

Revert to the legacy compiler from the miscellaneous tab of the preferences dialog.

 

Solution 2

 

The code splice is needed when the call to a user-defined function is just after the equal sign, and that call is followed by the addition of a string or an integer (this issue does not occur for void or Boolean user-defined functions).

 

Below are examples of code that will require splicing:

sTest = StrRoundedHour(nCurResIdx mod 1000000, '0') + '-test' // needs splicing
nCurResIdx = RoundedHour(12, '00000') + 3                     // needs splicing 

The solution is to add an empty string or 0 before the call to the user-defined function:

sTest = '' + StrRoundedHour(nCurResIdx mod 1000000, '0') + '-test' // no splicing needed
nCurResIdx = 0 + RoundedHour(12, '00000') + 3                      // no splicing needed 

In all cases, you might want to send your script or macro to technical support to look at it.

 

---

Topic 189095, last updated on 19-Aug-2026