EXPORT statement

Converts data to a standard character format and displays it to the current output destination (except when the current output destination is the screen) or to a named output stream. You can use data exported to a file in standard format as input to other ABL procedures.

EXPORT [ STREAM `stream` \| STREAM-HANDLE `handle` ] [ DELIMITER `character` ] { `expression` ... \| `record` [ EXCEPT `field` ... ] } [ NO-LOBS ]

EXPORT [ STREAM `stream` \| STREAM-HANDLE `handle` ] { `memptr` \| `longchar` }

The name of a stream. If you do not name a stream, the AVM uses the unnamed stream. See the DEFINE STREAM statement reference entry and the chapter on alternate I/O sources in OpenEdge Development: Programming Interfaces for more information on streams.

Specifies the handle to a stream. If handle it is not a valid handle to a stream, the AVM generates a run-time error. Note that stream handles are not valid for the unnamed streams. See the chapter on alternate I/O sources in OpenEdge Development: Programming Interfaces for more information on streams and stream handles.

The character to use as a delimiter between field values. The character parameter must be a quoted single character. The default is a space character.

If you specify more than one character as a delimiter, ABL uses the first character as the delimiter.

One or more expressions that you want to convert into standard character format for display to an output destination.

The name of the record buffer with fields that you want to convert into the standard character format to display to an output destination.

To use EXPORT with a record in a table name used in multiple databases, you must qualify the record’s table name with the database name. See the Record phrase reference entry for more information.

The AVM exports all fields except those fields listed in the EXCEPT phrase.

A variable of data type MEMPTR that contains the text to export. The EXPORT statement may contain a MEMPTR in its field list as long as it is the only field in the list.

A variable of data type LONGCHAR that contains the text to export. The EXPORT statement may contain a LONGCHAR in its field list as long as it is the only field in the list.

Directs the AVM to ignore large object data when exporting records that contain BLOB or CLOB fields.

This procedure converts the data in the Customer table into standard character format and sends that data to the customer.d file:

The next procedure shows how each EXPORT statement creates one line of data (that is, fields are not wrapped onto several lines):

r-exprt.p
OUTPUT TO customer.d. FOR EACH Customer NO-LOCK: EXPORT Customer. END. OUTPUT CLOSE.

r-exprt2.p
OUTPUT TO custdump. FOR EACH Customer NO-LOCK: EXPORT Customer.CustNum Customer.Name Customer.CreditLimit. END. OUTPUT CLOSE.

That procedure creates a text file, custdump, with one line for each Customer. This is a typical line of output:

Use the DELIMITER option to specify a character other than a space to separate fields in the output file. For example, the following procedure uses a semicolon:

The following example displays using a MEMPTR to EXPORT mixed character and binary data:

1 "Lift Line Skiing" 58400

r-cstout.p
OUTPUT TO custdump2. FOR EACH Customer NO-LOCK: EXPORT DELIMITER ";" Customer.CustNum Customer.Name Customer.CreditLimit. END. OUTPUT CLOSE.

1;"Lift Line Skiing";58400

r-expmem.p
/* Character and binary data mixed */ DEFINE VARIABLE z AS MEMPTR NO-UNDO. ASSIGN SET-SIZE(z) = 100 PUT-STRING(z,1) = "hi there" PUT-LONG(z,10) = 235 PUT-STRING(z,14) = "afterint" PUT-LONG(z,22) = 76. OUTPUT TO abc BINARY NO-CONVERT. EXPORT z. OUTPUT CLOSE.

The EXPORT statement must follow an OUTPUT TO statement, which redirects the output destination.

Other procedures can use the data exported with the EXPORT statement as input by reading the file with the INSERT, PROMPT-FOR, SET, UPDATE or IMPORT statements, naming one field or variable to correspond to each data element.

The data is in a standard format to be read back into ABL. All character fields are enclosed in quotes ("") and quotes contained in the data you are exporting are replaced by two quotes (""). A single space separates one field from the next. An Unknown value (?) is displayed as an unquoted question mark (?).

There are no trailing blanks, leading zeros, or formatting characters (for example, dollar signs) in the data.

ABL exports logical fields as the value YES or NO.

A Format phrase with an EXPORT statement is ignored.

If you use a single qualified identifier with the EXPORT statement, the Compiler first interprets the reference as dbname.tablename. If the Compiler cannot resolve the reference as dbname.tablename, it tries to resolve it as tablename.fieldname.

When exporting fields, you must use table names that are different from field names to avoid ambiguous references. See the Record phrase reference entry for more information.

When exporting RECID fields, you must explicitly state the RECID field name in the EXPORT statement.

When exporting ROWID variables or fields in a work table, you must convert the ROWID variable or field to a character string using the STRING function.

When exporting records that contain a BLOB or CLOB field, the AVM creates a separate object data file using a unique filename with a .blb extension and stores that filename in the BLOB or CLOB field of the exported record. (When importing records that contain a BLOB or CLOB field, the AVM uses this filename to locate the object data file associated with each record.) If the BLOB or CLOB field contains the Unknown value (?), the AVM stores the Unknown value (?) in the BLOB or CLOB field of the exported record, and does not create an object data file. If the BLOB or CLOB field contains a zero-length object, the AVM creates a zero-length object data file.

The AVM raises the ERROR condition if an object data file cannot be created.

The EXPORT statement creates large object data files in the directory specified as the output destination in the OUTPUT TO statement, by default. You can use the LOB-DIR option on the OUTPUT TO statement to specify the directory in which the EXPORT statement creates the BLOB and CLOB data files.

Use the NO-LOBS option with the EXPORT statement to ignore large object data when exporting records that contain BLOB or CLOB fields. When you specify the NO-LOBS option, the AVM stores the Unknown value (?) in the BLOB or CLOB field of the exported records and does not create the associated object data files.

When exporting DATETIME and DATETIME-TZ data, the data format is

fixed and conforms to the ISO 8601 standard for date/time representations (YYYY-MM-DDTHH:MM:SS.SSS+HH:MM). For DATETIME, there is no time zone offset.

If you use the DELIMITER option of the EXPORT statement to specify a delimiter other than a space character, you must specify the same delimiter character in a subsequent IMPORT statement that loads the data.

EXPORT is sensitive to the Date format (-d), Century (-yy), and European numeric (-E) startup parameters. When loading data with the IMPORT statement, use the same settings that you used with the EXPORT statement.

In the MEMPTR version of the EXPORT statement, the MEMPTR’s size will determine how much is written to the file. If the size of a MEMPTR is 100, and it only contains a string of length 10, the entire 100 bytes will still be written to the file. The PUT-BYTES statement and GET-BYTES function may be used to move portions of MEMPTRs to areas with varying sizes.You can read and write parts of a file by using MEMPTRs of varying sizes, and multiple EXPORT/IMPORT statements on the same file.

When dealing with Unicode CLOB and LONGCHAR variables, avoid using the EXPORT statement. The AVM uses the UTF-8 codepage for all Unicode EXPORTs. Use the COPY-LOB statement to avoid this conversion.

Never use APPEND while EXPORTing a LONGCHAR variable.