COMMANDUnder review

@ ... PSAY

@ nRow, nCol PSAY cText

Sends text for printing at a specified position.

@ ... PSAYAdvPL

01 · OVERVIEW

Overview

The eAdvpl reference guide, §13.2, p. 38, records the historical variant shown in the syntax. Fragments assume the matching environment and command definitions; they are not a complete application. The minimal historical syntax supplies row, column and text. Output setup, pagination, fonts and report closing belong to the environment printing flow. PSAY differs from a printer-object Say method and a dialog SAY command. Do not switch APIs while assuming identical coordinate units. This revision preserves the existing PSay route and clarifies its legacy scope. (Refs. 1)

02 · SYNTAX

Syntax

@ nRow, nCol PSAY cText

Parameters

nRow, nCol

NumericRequired

Origin position in the units of the selected variant.

cText

CharacterRequired

Text for an already configured print output.

Return value

Interface/printing command; do not use as a function-return expression.

03 · PRACTICAL EXAMPLE

Commented example

// Historical fragment: run only inside a configured printing flow.
Local cTitle := "Check summary"
@ 2, 4 PSAY cTitle
// Setup, pagination and closing are not included.

Expected result

Proposes one line on a prepared output; it does not independently generate a file or complete report. Under review: editorial example neither compiled nor run in Protheus. Check includes, release, RDD and context before testing.

BEST PRACTICES

Use a test output. Verify page breaks, accents, size and coordinate units; avoid sending real data to a printer just to test the fragment.
Under review: editorial example neither compiled nor run in Protheus. Check includes, release, RDD and context before testing.