Skip to main content

InvalidDateDayError

Procedure InvalidDateDayError(const AYear, ADayOfYear: Word)

Example​

procedure ScriptEvent(var Value: variant);
begin
  try
    InvalidDateDayError(2026, 367);
  except
    Value := 'Invalid date fields were rejected';
  end;
end;

Usage​

InvalidDateDayError raises the DateUtils invalid ordinal-date conversion error for supplied year and day-of-year fields.

Parameters

NameTypeDescription
AYearWord, constYear value included in the formatted error.
ADayOfYearWord, constOne-based ordinal day value included in the formatted error.

Behaviour

  • The procedure never returns normally.
  • Use IsValidDateDay when the script needs a Boolean range check rather than an exception.

Important usage notes

  • The routine does not check whether the year or ordinal day is actually invalid. Calling it with valid fields still raises.
  • The parameters are Word values, so negative numbers cannot be represented by the declared interface.

Errors

The intended and unconditional result is an EConvertError. The human-readable resource text can vary with the Velox runtime language or version; do not parse that message as a stable machine interface.

Usage notes

These DateUtils error helpers are principally useful to library code that has already detected invalid fields and wants the standard conversion error. Ordinary Velox scripts should normally validate first and provide business-specific handling rather than invoke this procedure directly.

Additional Technical Info​

InvalidDateDayError deliberately raises the DateUtils conversion exception for an invalid year and one-based day-of-year. It is an error-construction helper, not a validator.

The example is fictional and source-reviewed. It catches the deliberately raised exception so that the surrounding flow can continue; it was not executed by the documentation workflow.

Implementation

The DateUtils import binds directly to Delphi 37.0 System.DateUtils.InvalidDateDayError. The procedure formats the applicable DateUtils resource string with the supplied numeric fields and immediately raises an EConvertError.

Side effects

Control leaves the current statement by exception. There is no external I/O or persistent mutation.

Performance and concurrency

Formatting and raising one exception is constant-time but substantially more expensive than returning a Boolean. The routine has no mutable state of its own; resource and formatting behaviour is supplied by the host runtime.

Related entries

  • IsValidDateDay performs the associated non-raising field check.
  • InvalidDateTimeError builds the general date/time conversion error and has additional base-value and locale behaviour.

External references

Created 2026-07-15