To explain and better understand the information with this structure in this output format, we will use an example: the result of a reading operation. Specifically this is about the two reading records, with codes 2 and 3, from LK.CUSTOMERS record.
In the example that is shown below, line breaks have been added for a better explanation of their structure. Each different section is delimited by the ASCII 28 code (<FS>). In turn, inside each section, when there is an items list (as is our case, since 2 records have been read), the character ASCII 30 code is used (<RS>) to separate the items.
THIS_LISTþTOTAL_RECORDSþRECORD_IDþRECORD_ID_DICTSþRECORDþRECORD_DICTSþCALCULATEDþCALCULATED_DICTSþERRORS
<FS>
2
<FS>
2<RS>3
<FS>
@IDþCODE
<FS>
CUSTOMER 2þADDRESS 2þ444 - 444 – 002<RS>CUSTOMER 3þADDRESS 3þ444 - 444 - 003
<FS>
NAMEþADDRþPHONE
<FS>
<RS>
<FS>
<FS>
<FS>
In the first section a list of labels appears with the character þ (@AM attribute mark). Each label corresponds to each name of the following section. This way, the first section is called THIS_LIST, the second section TOTAL_RECORS, the third RECOR_ID, the fourth RECORD_ID_DICTS etc.
In the first section we find this first section and the rest of sections name.
In the second section (TOTAL_RECORD) we find the 2 value, because a total of 2 records have been read.
In the third section (RECORD_ID_DICTS) we find two dictionaries of Record Id. @ID and CODE.
In the fourth section (RECORD_ID) we find a records ID list. Since it is a list, the 2 and 3 ID´s are separated by the items separator character (<RS>).
In the fifth section (RECORD) we find the whole content of each record read. Since it is also a list, the (<RS>) character is used to separate the content of each record. The record content is shown just like it was in the database, preserving all its original marks: attribute marks (@AM), multivalue (@MV), subvalue (@SM) or Text (@TM).
In the sixth section (RECORD_DICTS) we find the names of the file dictionaries separated by the character þ (@AM attribute mark).
In the seventh section (CALCULATED) we would find the data from the calculated fields in each one of the 2 records read. Since this file has no calculated fields there is nothing to show, just the items separator character <RS>.
In the eighth section (CALCULATED_DICTS) the calculated field names. Since there are none this will be empty.
In the last section (ERRORS), if there were any, the error message would be shown.
More or less sections can appear depending on the operation and options of each operation. The section names always correspond with the same property names from the names of the LkData class properties. When the Read_Text was executed, the result of which we are using in this example, the Calculated option was activated inside its ReadOptions. Due to that, in this example, there are CALCULATED and CALCULATED_DICTS sections, although they are empty
If you wish you can experiment with the Linkar TRAINER program, executing Read functions, with different ReadOptions to see the different results. With this program, you can execute all the available clients functions with all their options
The complete list of MV labels is listed below:
THIS_LIST
RECORD_ID
RECORD_ID_DICTS
RECORD
RECORD_DICTS
CALCULATED
CALCULATED_DICTS
DICTIONARIES_ID
DICTIONARIES
ORIGINALRECORD
TOTAL_RECORDS
ARGUMENTS
CAPTURING
RETURNING
CONVERSION
FORMAT
ROWHEADERS
ERRORS
