Skip to main content

FileEvent

property FileEvent: TvxFileEventType read write;

Example

procedure ScriptEvent(var Value: Variant);
begin
if FileCon <> nil then
Value := Ord(FileCon.FileEvent)
else
Value := -1;
end;

Usage

FileEvent gets or sets FileCon's current Velox file-event marker, subject to a shifted script/Velox enumeration defect.

Critical enum mismatch

The script enum omits Velox fetDownload at ordinal 3, while the property helper passes the ordinal without translation.

Script value written/readOrdinalVelox meaning at that ordinal
fetNone0fetNone
fetRead1fetRead
fetWrite2fetWrite
fetAudit3fetDownload
fetError4fetAudit
fetIssue5fetError
fetTemp6fetIssue
fetTransport7fetTemp
fetDelete8fetTransport

Velox fetDelete is ordinal 9 and has no valid script enum label. The same table applies in reverse when reading Velox values: for example, a Velox audit event appears as script fetError.

Until the import is fixed, only fetNone, fetRead and fetWrite are aligned. Do not set or make business decisions from later script labels; use dedicated logging functions for actual audit/error/etc events and treat raw ordinals cautiously.

Side effects and ownership

The setter only changes the marker. It does not perform/log/verify a file operation, change CurrentFileName, register transport or persist configuration. Arbitrary script writes can change outbound routing behaviour (especially fetWrite) without any corresponding file creation.

Additional Technical Info

FileEvent is the current read/write/routing event marker used by file engines and outbound transport decisions.

Reset sets the native value to fetNone. File engines directly assign native fetRead or fetWrite; outbound transport creation checks native fetWrite to decide whether to iterate every recorded output file.

Performance and concurrency

Field access is constant-time and unsynchronised. Engines/actions can overwrite it as lifecycle state changes.

Related entries

Created 2026-07-15