-
GestBD: Database Tables management and maintenance
Access this help text as a web page: GestBD
Presentation and options
This application consists of a set of tools and procedures for editing, revising, updating, etc different elements (table structure, fields and records) of databases and tables. It is especially suitable for automating some of the procedures that are usually carried out interactively with the Table Manager MiraDades, but it also includes options that are exclusive to this application. The different procedures are explained in the detailed sections that appear below:
TEST_CONTINGUT_REGISTRES_DBF (1):
Carries out a series of consistency tests on DBF files. The program automatically solves all cases in different ways. The following is a list of errors detected and their solutions: - The text chains have been written with 0 characters at the end of their content. This is solved by erasing the 0 character and creating the missing spaces to the end of the cell, as is normal for DBF format.
- The numbers have been written with 0 characters at the end of their content. This is solved by erasing the 0 character and creating the missing spaces to the end of the cell, as is normal for DBF format.
- The text-type fields contain characters lower than the 32 ASCII character (e.g. tabulators). This is solved by replacing these characters with spaces.
- The numerical fields are not justified on the right. This is solved by moving the values within the cell to the right.
- The numerical fields contain non-numerical characters. This is solved by eliminating the values that contain errors (the whole cell is filled with blank spaces).
- The numerical fields contain the character ',' as a decimal separator. This is solved by replacing ',' with '.' which is the correct separator for DBF.
- The logic fields contain 0 or 1 values. This is solved by replacing the values with 'F' (false) or 'T' (true).
- The logic fields contain non-logic values. This is solved by blanking out the cells that contain errors.
- The data fields contain values that are not data. This is solved by blanking out the cells that contain errors.
- There are 'F'(float) type numerical fields when they could be 'N' (only numerical type in DBF). This is solved by changing the type of field from 'F' to 'N'.
- The file is longer than expected. There is data after the last record. It is resolved by truncating the file to the necessary size.
TEST_REGISTRE_MULTIPLE (2):
Eliminates the presence of multiple record for a graphic identifier of a MiraMon structured vectorial layer, (in other words, it converts the 1 to n ratio between the graphic base and the main table to a 1 to 1 ratio). The multiple records can be eliminated in two ways: by simply eliminating all the records except one (the first, the last, etc.) or by eliminating the fields that require the presence of multiple record because they show a variety of values for one graphic identifier. It should be noted that the presence of multiple record is not an error, but is, in most cases, an interesting property of the layer. However, in some situations you may not require this wealth of information and opt to generate a more simplified base by eliminating the multiple record.
PAS_DE_ODBC_A_DBF (3):
Allows the generation of a DBF table from a database that contains a link with any base or table using an ODBC driver (for example a Microsoft Access base in MDB format). With this database it is possible to generate a DBF table from any table or view of the database or from any SQL sentence.
SUPR_CAMP_DBF (4):
Eliminates one or more fields of a DBF table, including all the cells they contain.
CREA_CAMP_DBF (5):
Creates one or more fields of a DBF table with blank contents.
OMPLE_CAMP_DBF (6):
Fills the cells (indexed from 1) of a field with a constant value or with a sequence of values in autoincreasing.
CANVIA_CAMP_DBF (7):
Changes the following properties: descriptor, name, type, size or number of decimals, of one or more fields. It is necessary to specify all the properties indicated (with or without changes) in this order and field by field.
BUSCA_I_SUBS_CAMP_DBF (8):
Searches for all the records of a given chain or subchain and replaces them with another from where the search has found it.
FUSIONA_TAULES_DBF (9):
Merges n tables of identical structure into a single receiver table adding the records of the other tables at the end of the receiver table. The receiver table may already exist or not.
CONCATENA_CAMPS_DBF (10):
Merges n fields in a single existing receiver field. If you wish to add any character or constant chain for all the records at any position in the concatenation, this must be indicated by writing const(attribute), where attribute is a constant value. For example, if you want to concatenate some fields: day, month and year in a day-month-year format, it will be necessary to define a sequence as: day const(-) month const(-) year.
DUPLICA_CAMP_DBF (11):
Duplicates one or more consecutive fields and places them after a particular field.
MOU_CAMP_DBF (12):
Moves one or more consecutive fields and places them after a particular field.
MOSTRA_VALOR_CAMP_DBF (13):
Shows the contents of a field for a given set of records, indexed from 1.
JOIN_TAULES_DBF (14):
Allows the joining in a single table of fields belonging to two different DBF tables. It is necessary to establish a correspondence between both tables through one or several links between equivalent fields of the two tables; these fields are named key fields. In most cases there is enough with defining a single key field on each table (as it is stated in Example 1) in order to define clearly the correspondence between the records of both tables. In some cases, nevertheless, it is needed to define more than one key field in one or in both implied tables (Example 2) in order to define clearly the correspondence between both tables: the combination of these fields is called combined key. It is also needed to define all the fields which are shown in the output table, the result of join. If it is wanted that key fields appear in the output table too, they must be included in the desired field list because it may be desired that they only act as links, but not figuring in the resulting table of the join operation.
ORDENA_TAULA_DBF (15):
Carries out an ordering process for one or multiple criteria of a DBF table. The ordered table is generated in a new DBF file and it is possible to establish an ascending or descending order for each criterion.
SUPR_REGISTRE_DBF (16):
Eliminates one or more consecutive records of a DBF table. If it is wanted to specify a range, RegFi must be stated as well. RegFi record will be also erased.
JOIN_TOTS_ENLLACOS (17):
Makes as many joins as physical links is the main table and its associated tables, only to get a flat table (DBF format) with all fields of all tables associated, except the key fields of child tables that involve unnecessary repetition . The relationship indicated in the metadata rule style join (or RELACIO_1_N RELACIO_N_1). To perform this task, convert the ODBC tables to DBF, which can generate truncated in field names and changes of types and sizes. In addition, the maximum field name of the supertable is limited to 256 (limit of the resulting DBF).
MULTIREGISTRE_A_MULTICAMP (18):
Transforms multirecord into multifield. To define multirecord, repetitions of key field values is taken as a criterion (typically graphic identifier field). The fields are replicated as many fields as often as the maximum number of repetitions of the key field values.
DUPLICA_REGISTRE_DBF (19):
Generates duplicate records.
PAS_DE_ODBC_A_ODBC (20):
Allows the generation of a database table from another table, view or selection (from a SQL statement) of another database. Access to the database is via ODBC driver and therefore databases can be different from each other and from any type (MS Access, Oracle, SQL Server ...). The application will create a duplicate table, or view selection, following as closely as possible to the original format of the table when data types, sizes, restrictions ... (there are specific types of data each manager and there are no others, these chosen type with similar characteristics). This option is useful when we have systems database servers and types of information we need to send someone external not have access to the database, for example if we have a database type of Oracle or SQL Server. In this case, the information can be exported into a database such as MS Access, in order to have all data in a single file.
PURGA_TAULA_DBF (21):
Determines if there are records that have been marked as deleted but is still on the table. In this case, they are physically removed. The date of the file is only changed when records to be deleted are found. Most MiraMon programs ignore the erase mark and consider the records marked as deleted as normal records from the table. Whether it both Excel and Access does not show the records marked as deleted DBF's ODBC driver uses to execute a SQL statement DELETE.
OMPLE_CAMP_TANTP_CENT_A_DBF (22):
Fills a field with the percentage values obtained from the ratio of a field that contains a partial value and the total value.
COMPLETA_JOIN_1_A_N (23):
Completes the table with the values that can be missing in reviewing a JOIN 1 to N between the table and a thesaurus from the key fields that make the link and the fields to complete. Once the JOIN is established between the two tables, it is checked whether the values of the fields to be completed that come from the thesaurus are present in the table and otherwise, they are incorporated as more records for that graphic identifier.
ELEMENT_XML_A_DBF (24):
Writes in a cell of a DBF the XML node pointed by the xpath as a text. It is intended to retrieve the value of the "leaf" nodes of the document elements tree whether elements or attributes. In a document such as: 5400031_full28_ca to request the xpath "MD_Metadata/fileIdentifier" recovers: "5400031_full28_ca" to request the xpath "MD_Metadata/hierarchyLevel/MD_ScopeCode/@value" recovers: "series".
Remember that if the xpath of a node that is not "leaf" is requested, the values of all the child elements separated by spaces will be obtained, result that does not seem too useful.
Be careful with xpath like this: /bookstore/book[1]/title "IE5 and later has implemented that [0] should be the first node, but according to the W3C standard it should have been [1]. In MiraMon, using Windows libraries (which are from IE5) is this "characteristic", that is to say, that the arrays of nodes begin to be numbered from 0 and not from 1.
CONVERTEIX_EXPRESSIO_EN_RESULTAT (25):
Changes a written expression in a field for its result. Currently the only supported expression is xpath().
CREA_REGISTRE_BUIT_DBF (26):
Creates an empty record in the DBF table.
PAS_DE_ESTESA_A_CLASSICA (27):
Converts a MiraMon extended DBF to classical DBF format (dBASE III, dBASE III+ o dBASE IV).
MOSTRA_RMS_DE_CAMP (28):
Calculates the RMS of a field in a DBF and displays it on the screen.
GENERA_TESAURUS (29):
Generates a thesaurus from the projection of the indicated field.
Many of these options are part of the processes that can be linked together in a BAT program (see MiraMon Support Applications) and are part of a set of more complex database management procedures. The functionality of this application is to provide this set of very specific tools which, within a more global management procedure, will make it possible to carry out adjustments to the database arising from other processes and/or the preparation of the database in order to verify specific necessary conditions before starting up other processes.
Dialog box of the application
Graphic examples
Example 1 --> Join via a single key field.
Join of Taula1.dbf (Table1.dbf in English) and Taula2.dbf (Table2.dbf in English) via the common field ID (marked with a red rectangle in the figure). In this example, it is desired that table Resultat.dbf (Result.dbf in English) contains all the fields which are present in both tables without repeating the equivalent fields in both tables.
GestBD 14 Resultat.dbf Taula1.dbf Taula2.dbf /T1_CLAU1=ID /T2_CLAU1=ID /T1_CAMP1=ID /T1_CAMP2=CITY /T1_CAMP3=POPULATION /T1_CAMP4=KM2 /T2_CAMP3=REGION /T2_CAMP4=COUNTRY /RELACIO_1_N /NOMES_REG_ENLLAC
Example 2 --> Join via two key fields on each table.
Join of Taula1.dbf and Taula2.dbf via the common key fields STATIONID and REGION of Taula1.dbf, and fields ID and REGIONID of Taula2.dbf (all of them marked with a red rectangle). In this example it is wanted table Resultat.dbf to contain all the fields which are present in both tables without repeating the equivalent fields in both tables.
Note: Key fields must have the same structures (Type and Extent), although it is not necessary to have the same name.
GestBD 14 Resultat.dbf Taula1.dbf Taula2.dbf /T1_CLAU1=STATIONID /T1_CLAU2=REGION /T2_CLAU1=ID /T2_CLAU2=REGIONID /T1_CAMP1=STATIONID /T1_CAMP2=REGION /T1_CAMP3=COORDX /T1_CAMP4=COORDY /T1_CAMP5=COORDZ /T2_CAMP1=CITYNAME /RELACIO_1_N /NOMES_REG_ENLLAC
Syntax
Syntax:
- GestBD 1 DBFFile [/APLICAR]
- GestBD 2 DBFFile [/APLICAR] [/ELIMINAR_CAMPS] [/REG_TOT_IGUAL]
- GestBD 3 DBFFile Table
- GestBD 4 DBFFile FieldName [FieldNameUntil]
- GestBD 5 DBFFile FieldNameAfter FieldDesc FieldName Type Size NDecimals
- GestBD 6 DBFFile FieldName IniRec FiRec Value [Increment]
- GestBD 7 DBFFile PrevFieldName FieldDesc FieldName Type Size NDecimals
- GestBD 8 DBFFile FieldName SearchedValue ReplacedValue [/VALOR_COMPLET] [/INSENSIBLE_MAJ] [/TRACTAR_N_COM_C]
- GestBD 9 ReceiverDBFFile DonorDBFFile
- GestBD 10 DBFFile ResultingField Field
- GestBD 11 DBFFile FieldName [FieldNameUntil] [FieldNameAfter]
- GestBD 12 DBFFile FieldName [FieldNameUntil] [FieldNameAfter]
- GestBD 13 DBFFile FieldName IniRec FiRec
- GestBD 14 DBFResultFile MainDBFFile SecondaryDBFFile [/T1_CLAU#] [/T2_CLAU#] [/T1_CAMP#] [/T2_CAMP#] [/RELACIO_1_N] [/NOMES_REG_ENLLAC]
- GestBD 15 DBFResultFile OriginDBFFile [/CAMP_#] [/ORDRE_#]
- GestBD 16 DBFFile IniRec [FiRec]
- GestBD 17 DBFResultFile DBFMainTable
- GestBD 18 DBFFile FieldKeyName FieldName [FieldNameUntil] [FieldNameAfter]
- GestBD 19 DBFFile IniRec [RecAfter]
- GestBD 20 BDResultFile DBOriginFile OriginTable ResultTable
- GestBD 21 DBFFile
- GestBD 22 DBFFile FileNamePcent FileNamePartial FileNameTotal [/SUMA_CENT]
- GestBD 23 DBFFile SecondaryDBFFile [/T1_CLAU#] [/T2_CLAU#] [/T1_CAMP#] [/T2_CAMP#]
- GestBD 24 DBFFile XMLFile IniRec FieldName XPath [WhatExtract]
- GestBD 25 RELFile
- GestBD 26 DBFFile IniRec [HowMany]
- GestBD 27 ExtendedDBFFile ClassicalDBFFile
- GestBD 28 DBFFile RMSFieldName [NODATA]
- GestBD 29 DBFThesaurusFile DBFFile FieldName [/TRACTAR_N_COM_C]
Options:
- 1:
Consistency test of contents of one DBF.
- 2:
Elimination of the multiple record by graphic object of one DBF.
- 3:
Conversion of an ODBC table to a DBF table.
- 4:
Elimination of a field or a set of fields of a DBF table.
- 5:
Creation of one or more fields of a DBF table.
- 6:
Filling the values of a field with a constant or an autoincreasing value.
- 7:
Changing of descriptor, name, type, size or number of decimals of one or more fields of a DBF table.
- 8:
Searching and replacement within a DBF field.
- 9:
Merging n tables of identical structure into a single receiver table.
- 10:
Merging n fields in a single pre-existing receiver field. In order to add, at any position in the concatenation, any constant character or string for all records, type const(attribute), where attribute is a constant value.
- 11:
Duplicating one or more consecutive fields and places them after a given field.
- 12:
Moving one or more consecutive fields and places them after a given field.
- 13:
Showing the contents of a field for a set of records, indexed from 1.
- 14:
Generating a new resulting table (DBFFileResulting) from a join between the DBFFileMain and DBFFileSecondary tables with one or multiple links. The links are indicated from the key fields /T1_CLAU# (for table 1) and /T2_CLAU# (for table 2) and the fields present in the resulting table are indicated from their origins with /T1_CAMP# (for table 1) and /T2_CAMP# (for table 2). # is the field number, indexed from 1 for each table.
- 15:
Generates a new resulting table (DBFFileResulting) from an ordering defined by one or n criteria indicated by /CAMP_#. For each field or criterion it is possible to define an ascending (default) or descending order using /ORDRE_#.
- 16:
Eliminates one or more consecutive records of a DBF table. If you wish to specify an interval, you should also indicate FiRec. The FiRec record will also be erased.
- 17:
Generates the 'flat table' (not relational) DBFResultFile, from the physical joins between the main table and associated tables indicated in the corresponding DBFMainTable REL file.
- 18:
Transforms multirecord into multifield. To define multirecord, repetitions of key field values is taken as a criterion (typically graphic identifier field). The fields between FieldName FieldNameUntil are replicated to multiple fields with a similar name (with an incremental index added) as many times as the maximum number of repetitions of values FieldKeyName (they are added after the field FieldNameAfter; typically FieldNameAfter and FieldNameUntil are the same).
- 19:
Generates duplicate records in a new position.
- 20:
Allows the generation of a database table from another table, view or selection (from a SQL statement) of another database.
- 21:
Records that have been marked as deleted are physically removed from the file.
- 22:
Fills a field with the percentage values obtained from the ratio of a field that contains a partial value and the total value.
- 23:
Completed the result table (FileDBF) with the values that may be missing in reviewing a 1 to N join between the DBFFile and the DBFfileSecondary from one or multiple links.
- 24:
Fills a cell in a DBF with the values (if QueExtr='V') or the names (if QueExtr='N') of an element or attribute designated by an XPath of an XML document. If the XPath results in more than one item, it fills more than one consecutive record for that field. In case (if QueExtr='C') it fills the cell with the number of nodes that meet the xpath.
- 25:
Changes an xpath() expression written in a field for its result.
- 26:
Creates an empty record.
- 27:
Converts an extended DBF file to classical DBF file.
- 28:
Calculates the RMS of a field in a DBF and displays it on the screen.
- 29:
Generates a thesaurus from the projection of the indicated field.
Parameters:
- DBFFile
(DBF File -
Input parameter): File in classical DBF format (dBASE III, dBASE III+ or dBASE IV) or extended DBF of MiraMon.
- DBFile
(Data Base File -
Input parameter): DSN file or a file-type database (as it is an MDB) accessible through ODBC.
- Table
(Table -
Input parameter): Table, when the origin is indicated, it may be a table, view or an SQL query about the ODBC database (if the sentence requires inverted commas, a diaresis must be used instead); when table is the result, it only can be a table.
- FieldName
(Field Name -
Input parameter): Name of the field of the DBF table.
- FieldNameUntil
(Field Name Until -
Input parameter): Field name that closes the interval, or '*' if you wish to continue until the last field.
- FieldNameAfter
(Field Name After -
Input parameter): Name of the field after which the selected operation is carried out (create, erase, etc), or '*' if it must be done before the first or ']' if it must be done after the last.
- FieldDesc
(Field Descriptor -
Input parameter): Descriptor of the field.
- Type
(Field Type -
Input parameter): Type of field.
- Size
(Field Size -
Input parameter): Size of the field.
- NDecimals
(Decimals Number -
Input parameter): Number of decimals of the field, select 0 if it is not numerical.
- IniRec
(Initial Record -
Input parameter): Record index starting from 1 where it starts working or '*' starting from the end of the table.
- FiRec
(Final Record -
Input parameter): Record index starting from 1 where it stops working or '*' in order to continue until the end of the table.
- Value
(Value -
Input parameter): Numerical or alphanumerical value to initialize the records or the initial numerical value where the records begin with an autoincrease.
- Increment (Input parameter): In order to apply an auto-increment you must indicate its value. If no value is indicated, the records will be initialized at a constant value.
- PrevFieldName
(Previous Field Name -
Input parameter): Name of the field of the DBF table to be changed. You may indicate a field index (field number starting from 1) preceded by the symbol # (e.g. #12).
- SearchedValue
(Searched Value -
Input parameter): Numerical or alphanumerical value to be searched for in the field of a DBF.
- ReplacedValue
(Replaced Value -
Input parameter): Numerical or alphanumerical value replaced in a field of a DBF.
- ReceiverDBFFile
(Receiver DBF File -
Output parameter): Receiver DBF file (result) in classical DBF format (dBASE III, dBASE III+ or dBASE IV) or extended DBF of MiraMon.
- DonorDBFFile
(Donor DBF File -
Input parameter): Donor DBF file in classical DBF format (dBASE III, dBASE III+ or dBASE IV) or extended DBF of MiraMon.
- ResultingField
(Resulting Field -
Input parameter): Field name of the resulting table.
- Field
(Field To Merge # -
Input parameter): Name of the fields that will be merged into one.
- DBFResultFile
(DBF Result File -
Output parameter): DBF result file in classical DBF format (dBASE III, dBASE III+ or dBASE IV) or extended DBF of MiraMon.
- MainDBFFile
(Main DBF File -
Input parameter): Main DBF file of the fusion on tables in classical DBF format (dBASE III, dBASE III+ or dBASE IV) or extended DBF of MiraMon.
- SecondaryDBFFile
(Secondary DBF File -
Input parameter): Secondary DBF file of the fusion on tables in classical DBF format (dBASE III, dBASE III+ or dBASE IV) or extended DBF of MiraMon.
- OriginDBFFile
(Origin DBF file -
Input parameter): DBF origin file in classical DBF format (dBASE III, dBASE III+ or dBASE IV) or extended DBF of MiraMon.
- DBFMainTable
(DBF Main Table -
Input parameter): Main table file in classical DBF format (dBASE III, dBASE III+ or dBASE IV) or extended DBF of MiraMon.
- FieldKeyName
(Field Key Name -
Input parameter): Name of the field of the DBF table that acts as a key field.
- RecAfter
(Record After -
Input parameter): Record index starting from 1 where is it inserted the new record.
- BDResultFile
(BD Result File -
Output parameter): Result database. DSN file or a file-type database (as it is an MDB) accessible through ODBC.
- DBOriginFile
(DB Origin File -
Input parameter): Origin database. DSN file or a file-type database (as it is an MDB) accessible through ODBC.
- OriginTable
(Origin Table to convert -
Input parameter): It may be a table, view or an SQL query about the ODBC database (if the sentence requires inverted commas, a diaresis must be used instead).
- ResultTable
(Result Table -
Input parameter): Table result of the conversion.
- FileNamePcent
(File Name % -
Input parameter): Field to be filled with the values obtained from the ratio of FileNamePartial and FileNameTotal.
- FileNamePartial
(File Name partial -
Input parameter): File Name Partial
- FileNameTotal
(File Name Total -
Input parameter): File Name Total
- XMLFile
(XML File -
Input parameter): XML File
- XPath (Input parameter): Xpath of the XML document referring to the part of the document to extract the information.
- WhatExtract
(What to extract -
Input parameter): If QueExtr='V' fills the cell with the value of the element or the attribute designated by a XPath, if QueExtr='N' fills the cell with the name of the element or the designated attribute for a XPath and if QueExtr='C' fills the cell with the number of nodes that meet the xpath.
- RELFile
(REL File -
Input parameter): REL file that links or describes a file in classical DBF format (dBASE III, dBASE III+ or dBASE IV) or extended DBF of MiraMon.
- HowMany
(How Many -
Input parameter): Number of elements or records to be created.
- ExtendedDBFFile
(Extended DBF File -
Input parameter): Extended DBF file of MiraMon.
- ClassicalDBFFile
(Classical DBF File -
Output parameter): DBF file in classical format (dBASE III, dBASE III+ or dBASE IV).
- RMSFieldName
(RMS Field Name -
Input parameter): Name of the field in the DBF table of which the RMS is calculated.
- NODATA
(NoData Value -
Input parameter): NoData value of the field from which the RMS is calculated.
- DBFThesaurusFile
(DBF Thesaurus File -
Output parameter): Thesaurus file resulting from the projection of the field of the indicated DBF file. File in classical DBF format, (dBASE III, dBASE III+ or dBASE IV) or extended DBF of MiraMon.
Modifiers:
/APLICAR (Apply) Implements solutions to the problems detected in the text. (Input parameter) /ELIMINAR_CAMPS
(Eliminates fields)
Eliminates the fields that made the presence of multiple record necessary. (Input parameter) /REG_TOT_IGUAL
(DBF record fully equal)
Remove the DBF record fully equal and therefore eliminates the multiple log reduntant entirely. This may not be particularly useful when there are numeric fields that can refer to values to be totalize among the multi-records. (Input parameter) /VALOR_COMPLET
(Full Value)
Indicates that the value being searched must coincide with all the value of the field record. (Input parameter) /INSENSIBLE_MAJ
(Insensible Capital Letters)
The search is carried out without taking into account upper or lower case letters. (Input parameter) /RELACIO_1_N
(1 to N relation)
Indicates that a multiple cardinality relationship is possible between a record of the main table and n records of the associated table. Its absence does not permit this multiple relationship. (Input parameter) /NOMES_REG_ENLLAC
(Only Records Link)
This parameter implies that only are stored in the result table those records contained in the main table that have correspondence in the associated table. (Input parameter) /CAMP_#=
(CAMP_#)
Names of the fields that will be part of the resulting table. # is an order number (correlative and starting from 1). (Input parameter) /ORDRE_#=
(ORDRE_#)
"D" or "d "indicates a descending order and "A" or "a" an ascending order (default). (Input parameter) /SUMA_CENT
(Up to 100)
Calculated percentages add up to 100. (Input parameter) /T1_CLAU#= (T1_CLAU#) Names of the key fields of the main table T1, with which the connection between the two tables is established in order to carry out the join. # indicates the order of the key fields linked, indexed from 1. If more than one field is stated, it is understood that it is desired to perform as a combined key. (Input parameter) /T2_CLAU#= (T2_CLAU#) Names of the the key fields of the associated table T2, with which the connection between the two tables is established in order to carry out the join. # indicates the order of key fields linked, indexed from 1. If more than one field is stated, it is understood that it is desired to perform as a combined key. (Input parameter) /T1_CAMP#= (T1_CAMP#) Names of the fields of the T1 table that will make up the resulting table. # indicates the order (correlative and beginning by 1). (Input parameter) /T2_CAMP#= (T2_CAMP#) Names of the fields of the T2 table that will make up the resulting table. # indicates the order (correlative and beginning by 1). (Input parameter) /TRACTAR_N_COM_C (Treating numbers like string) Indicates that the numbers are treated as chains of characters. (Input parameter)
