Please enable JavaScript to view this site.


Navigation: Messages > Run-Time Messages > Token Syntax

Incorrect syntax for year offset token

Scroll Prev Up Next More

This error occurs when evaluating a year offset token, if the 3 characters following the colon do not represent a number.


For example:




The token is read without the braces, and that only having 2 characters after the colon is still acceptable, as long as these 2 characters represent a valid number, for example: [1yyyy:+1].


Note that there is a more general suffix to add days, months or years to any token.


Topic 174385, last updated on 17-Apr-2020