Xobas Software'> ]> Documentation for ProLinga System Builder Release: &version; - &release-date; Bas Driessen &xobas;

bas.driessen@xobas.com

Original author and current maintainer. 2002-©right-year; The ProLinga Team Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License". This document contains the 4GL Reference Manual. &cmd_break; &cmd_call; &cmd_clear; &cmd_comment; &cmd_continue; &cmd_control; &cmd_datamodel; &cmd_display; &cmd_else; &cmd_elseif; &cmd_endfor; &cmd_endif; &cmd_error; &cmd_focus; &cmd_for; &cmd_foreach; &cmd_forever; &cmd_if; &cmd_let; &cmd_list; &cmd_message; &cmd_nil; &cmd_parameter; &cmd_progress; &cmd_repository; &cmd_response; &cmd_return; &cmd_run; &cmd_screen; &cmd_sleep; &cmd_sql; &cmd_text; &cmd_transaction; &cmd_thread; &cmd_xml; In the Screen Painter, widget event signals can be linked to action handlers. The following action handlers are available: Control C-control_name (built-in function) Logic L-logic_name Screen S-screen_name There are three types of data reference items: Single Data Reference Item Group Data Reference Item Definition Data Reference Item In the Screen Painter, widget event signals can be linked to a data reference move. With the prefix D:GET:data_ref a value will be moved FROM the single data reference TO the screen widget. With the prefix D:PUT:data_ref a value will be moved TO the single data reference FROM the screen widget. Blob B-blob_name Constant C-constant_name (read-only) Error E-error_name (read-only) Table Field F-data_dictionary_name.table_name[.record_name] Variable Group Field G-data_dictionary_name.variable_group_name Local Variable Field L-data_dictionary_name Data Model Field M-_col_xx.data_model_name M-external_field_name.data_model_name M-alias.data_model_name Pick List P-pick_list_name(entry) Variable V-variable_name Text X-text_name From logic, certain objects containing child entries can be referenced within a single command to copy all entries. VariableGroup H-variable_group_name DataModel O-data_model_name Record R-table_name[.record_name] Within SQL commands, names like column name or table name must be available. Data Dictionary D-data_dictionary_name (read-only) Table T-table_name (read-only) From within logic, many special built-in functions (controls) can be called. The following are available: APPN() Returns the name of the application. APPNDEV() Returns the name of the application being developed. ASCII(data_ref) Converts integer into corresponding ASCII character. CLIP(data_ref) Clip leading and trailing blanks from data_ref. COMPILEINFO() Returns information of how the binary is compiled by printing the linked in ProLinga Components. CONFIGFILE() Returns the path and name of the default configuration file. DATAMODELSTATUS() Contains the error number of the last executed DATAMODEL command. 0 means no error. DATE() Returns the current date. ERRORRETURN() Contains the use selection value of a QUESTION error. 0 = YES, 1 = NO. EXPANDINSERT(record_name) Expands the values of a Record in a comma separated value list, so it can be used as a short cut for a sql insert operation. EXPANDUPDATE(record_name) Expands the values of a Record in a comma separated name=value list. so it can be used as a short cut for a sql update operation. FALSE() Returns value set as False value in the Administrator Application. LENGTH(data_ref) Returns the length of data_ref. LISTCOLCOUNT(data_ref) Returns the number of columns of in list store data_ref. LISTROWCOUNT(data_ref) Returns the number of rows of in list store data_ref. NEWLINE() Returns a newline (\n) character. Typically used in combination with the TEXT command. QUITLASTSCREEN() If set to 0, the application exits after the last screen has been closed. REPOSITORYINFO(data_ref) Returns repository system info. The following data_ref are available: ServiceId, ServerHost, ServerPort, SystemPath, NumberOfThreads, LogFile, LogLevel, ServerCompressionLevel, SystemHostName. REPOSITORYSTATUS() Contains the error number of the last executed REPOSITORY command. 0 means no error. SQLINFO() Contains (error) information generated by 3rd party data provider regarding last executed SQL command. SQLRETURN() Contains the number of rows affected of the last ACTION SQL statement. SQLSTATUS() Contains the error number of the last executed SQL or TRANSACTION command. 0 means no error. TEXTSTATUS() Contains the error number of the last executed TEXT command. 0 means no error. TIME() Returns the current time. THREADEXIT() True/False switch if logic executed in a thread should continue or exit. THREADSTATUS() Contains the error number of the last executed THREAD command. 0 means no error. TOLOWER(data_ref) Changes characters to lowercase where possible. TOUPPER(data_ref) Changes characters to uppercase where possible. TRUE() Returns value set as True value in the Administrator Application. USER() Returns the name of the user logged on to the environment. VERSION() Returns the version number of the binary. WEBPARAMETER(data_ref) Returns value from a web browser argument. XMLSTATUS() Contains the error number of the last executed XML command. 0 means no error. All application objects needed to execute 4GL applications are stored as XML documents in the (remote) application repository. All these objects are stored with the following unique key combination: Application Object Name There are two types of these base objects: System Objects these objects apply to the environment in which applications run. The objects will be stored in the administrator application. Application Objects these objects apply to a specific application only. &obj_application; &obj_system; &obj_user; &obj_version; &obj_blob; &obj_constant; &obj_datadictionary; &obj_datamodel; &obj_datasource; &obj_errordialog; &obj_index; &obj_liststore; &obj_logic; &obj_picklist; &obj_record; &obj_runcontrol; &obj_screen; &obj_table; &obj_textdocument; &obj_thread; &obj_variable; &obj_variablegroup; &obj_xmldocument; Many 4GL commands return a status to indicate if a command was processed succesfully or to provide extra information on the processed command. Error messages are displayed to inform the user what went wrong. This section documents the various error and status information. &error_status; &fdl;