ENTRY POINTUnder review

F460EDIT

User Function F460EDIT()

Interest-field validation in the legacy editing screen.

F460EDITFINA460

01 · OVERVIEW

Overview

In the public copy, the nValJur MSGET combines Fa460Val with ExecBlock through .AND. and passes nValJur directly, without {nValJur}. The result participates in logical field validation rather than replacing the interest amount. The official index does not detail this contract; confirm it in the target release. (Refs. 1 and 3) Research includes indexed TDN evidence; no complete specific page was recovered.

02 · SYNTAX

Syntax

User Function F460EDIT()

Parameters

Entry point context

UnconfirmedContext to confirm

The complete technical contract remains unconfirmed. Do not assume types, PARAMIXB positions or aliases beyond the evidence described.

Return value

Logical consumed by .AND. in the observed caller; not the new interest amount.

03 · PRACTICAL EXAMPLE

Observed call and context

// Analysis of a legacy caller published on GitHub (ref. 3); not a hook implementation.
// // MSGET nValJur / Valid:
// Fa460Val(nValOri,nValBxd,nValJur+nMora,nValDes,nValAbt,@nValLiq,,nMoedaTit,nValCvt,nCotMoed) .AND. ExecBlock("F460EDIT",.F.,.F.,nValJur)

Expected result

The record shows arguments and immediate return use where present. It omits the full caller body and does not establish commit timing.

BEST PRACTICES

The GitHub copy does not identify a validated release and is not an official distribution. Check the caller in the target environment; this example analyzes legacy flow rather than providing a deployable function.
A call without a fourth argument does not document a PARAMIXB layout. Preserve caller identifiers and do not invent fields or positions.
Test plan: compare standard and customized flows, exercise success, rejection and repetition, and inspect balances, movements and accounting as applicable.
Under review: example not compiled or run in Protheus. Verify aliases, locks, transaction position and compatibility in the target release and patch.