PRACTICAL GUIDEUnder review

TCSqlExec and SQL statement execution

TCSqlExec(cStatement) -> nStatus

Executes one SQL statement on the current DBAccess connection.

TCSqlExec and SQL statement executionAdvPL

01 · OVERVIEW

Overview

TCSqlExec returns a negative numeric status on failure; do not treat it as affected-row count. Statements depend on the DBMS. TDN warns that direct SQL does not update DBAccess control fields. The community example updates a custom product field; this page analyzes the pattern without reproducing a master-data update. The uninvoked block only prepares execution. Connection/transaction owners must define SQL and error handling. (Sources: refs. 1–2.)

02 · SYNTAX

Syntax

TCSqlExec(cStatement) -> nStatus

Parameters

cStatement

CharacterRequired

SQL statement for the authorized DBMS/context.

Return value

Numeric; negative indicates failure.

03 · PRACTICAL EXAMPLE

Commented example

#Include "Protheus.ch"

User Function Ed688()
    // Do not invoke with external SQL: define a statement in an isolated lab.
    Local bExecute := {|cStatement| TCSqlExec(cStatement)}
    ConOut(ValType(bExecute))
Return Nil

Expected result

Creates block B without SQL execution. During integration check status < 0 and retrieve TCSQLError in the failure context. Under review: editorial example neither compiled nor run in Protheus. Check includes, release, RDD and context before testing.

BEST PRACTICES

Use one statement per call; neither concatenate external input nor bypass ERP business rules.
Under review: editorial example neither compiled nor run in Protheus. Check includes, release, RDD and context before testing.