RetProfDef
RetProfDef(...) -> cRetReads profile definitions with unresolved call arity.
Overview
The P10 TDN page describes returning user-profile definitions. Its syntax lists P1 while the parameter description enumerates UserCode, ProgramName, task and type as P1 through P4. It does not resolve whether these are separate arguments or document defaults. This page therefore does not invent a four-argument signature. The example only organizes fictional criteria in memory; it neither calls RetProfDef nor reads user preferences. (Sources: refs. 1–1.)
Syntax
RetProfDef(...) -> cRetReturn value
cRet: record definitions according to the P10 page; detailed format unspecified.
Commented example
#Include "Protheus.ch"
User Function Ed627()
// Criteria mentioned by TDN; this is NOT an API call.
Local aCriteria := {"USER_TEST","ED627","TASK_TEST","TYPE_TEST"}
ConOut(Len(aCriteria))
Return NilPrints 4, only the criteria count in this exercise. This does not establish API arity. Under review: editorial example neither compiled nor run in Protheus. Check includes, release, RDD and context before testing.
- Confirm the release signature before invoking. A profile does not represent authorization.
- Under review: editorial example neither compiled nor run in Protheus. Check includes, release, RDD and context before testing.
Comments
There are no approved comments yet.
Sign in with Google or Microsoft to comment.