PPWIZARD Manual
#import - Multi Line Records
This type of #Imports
have clearly defined fields which you label.
You would frequently wish to display these in a table (say in
a HTML page) however nothing says that you need to do so.
Field Information Parameters
On these types of imports "FieldInfo" followings
the "DefineName" parameter.
For each field you have defined in your database you must specify
field information.
The field information is of the format:
{*,FieldName[,FieldOptions]}TitleText
In place of the '*' you could specify the column number you wish to
place the field but its usually easier to simply reorder the fields.
The "field name" specifies the name you use in your database. It
can contain virtually any characters but must of course not contain the
delimiter character ('=' by default). Like all PPWIZARD names the
name can contain international characters.
You can optionally specify some field options which vary the way
individual fields are processed. Each field option is separated by a
comma, valid options are:
- REQUIRED
This field is required. You can supply a blank value.
This validation occurs whether or not the field is dropped.
- NONBLANK
This field if supplied must be non blank.
If not supplied its value will become blank unless
"REQUIRED" option was also specified.
This validation occurs whether or not the field is dropped.
- NOASIS
By default all files go through AsIs() replacements, this option
allows you to prevent this occuring on particular fields if
required.
The "title text" specifies the value for the field in the
header record. Since all fields must be defined we use a blank "title"
to indicate that we don't require a field and it should be dropped.
DEFINITIONS/OPTIONS
If you can't understand how these options work then I suggest
you try using /debug or #debug to
watch what variables the import uses etc.
- DefineName_BLANK_FIELD
Normally a blank field will be displayed as blank.
You may wish to display '-' instead.
Another possiblity is to display a 1 by 1 transparent gif so as
to have table borders around blank fields look better.
For even more control (probably rare requirement):
- DefineName_BLANK_COLUMN_?
This allows you to specify different blank replacement
values for each column.
- DefineName_TAB_CHAR
Normally tabs are ignored by the import process. This variable allows you to replace them with something else.
- DefineName_ASIS_TAGGING
This option can be used to adjust the conversion of what may be problem characters (such as '<' in HTML). By default
importing does not handle/convert international characters such as umlauts to html symbols but there is nothing preventing you from doing so.
This definition lists zero, one or more names as used on previous "#AsIs SETUP" commands (seperated by whitespace). Clear this definition to prevent all ASIS conversions.
Note that you will probably need to override this value (maybe others as well) if you wished to expand any macros
that the imported data might contain (by default this is not done).
- DefineName_BEFORE
You would probably only use this define if you didn't want to
generate a table at all. You may specify the string
"{$Columns}" which will get replaced with the number of
fields to be displayed.
If this define is not used then you can use the following:
- DefineName_TABLE_ATTRIBS
This value allows you to specify all HTML attributes of the
table apart from the number of columns.
- DefineName_HEADER
This is used to control the "code" which handles the "heading" record,
this does not have to be a html table.
You can specify the string {$Column?} to
represent a fields value (? = number of field where 1 is the first).
If this define is not used then you can use the following:
- DefineName_HEADING_COLUMNS
This value allows you to specify the column (HTML "<TH>" tags)
information to change alignment or colours of columns.
This value becomes the default for all columns.
- DefineName_HEADING_COLUMN_?
This value allows you to specify the column (HTML "<TH>" tags)
information to change alignment or colours of specific columns.
Another use for this would be to specify the width of a column.
This value is only used for column number '?'.
- DefineName_HEADING_BEFORE_DATA
This value allows you to specify some text to be placed in front
of the fields data, for example if you wish to change the font size
for each column you might used the value
"<FONT SIZE=-1>".
This value becomes the default for all columns.
- DefineName_HEADING_BEFORE_DATA_?
This value allows you to specify leading data on a column by
column basis.
- DefineName_HEADING_AFTER_DATA
This value allows you to specify some text to be placed after
the fields data, for example if you wish to change the font size
for each column you might used the value
"</FONT>" to close the previous font tag.
This value becomes the default for all columns.
- DefineName_HEADING_AFTER_DATA_?
This value allows you to specify trailing data on a column by
column basis.
- DefineName_RECORD
This is used to control the "code" for each record,
this does not have to be a html table.
You would definately define this option if you didn't want a html
table, you might wish to create s series of #defines or maybe you are
not generating html at all and need to generate an IPF table.
You can specify the string {$Column?} to
represent a fields value (? = number of field where 1 is the first).
If this define is not used then you can use the following:
- DefineName_RECORD_COLUMNS
This value allows you to specify the column (HTML "<TD>" tags)
information to change alignment or colours of columns.
This value becomes the default for all columns.
- DefineName_RECORD_COLUMN_?
This value allows you to specify the column (HTML "<TD>" tags)
information to change alignment or colours of specific columns.
Another use for this would be to specify the width of a column.
This value is only used for column number '?'.
- DefineName_RECORD_BEFORE_DATA
This value allows you to specify some text to be placed in front
of the fields data, for example if you wish to change the font size
for each column you might used the value
"<FONT SIZE=-1>".
This value becomes the default for all columns.
- DefineName_RECORD_BEFORE_DATA_?
This value allows you to specify leading data on a column by
column basis.
- DefineName_RECORD_AFTER_DATA
This value allows you to specify some text to be placed after
the fields data, for example if you wish to change the font size
for each column you might used the value
"</FONT>" to close the previous font tag.
This value becomes the default for all columns.
- DefineName_RECORD_AFTER_DATA_?
This value allows you to specify trailing data on a column by
column basis.
- DefineName_AFTER
Unless you are not creating a table you are unlikely to want to
change the codes that end the table.
- DefineName_RECORD_FILTER
The contents of this variable should be one or more
rexx expressions.
Normally all records are displayed.
A filter can examine all column variables and modify them or tell
PPWIZARD to ignore the record. The filter is not called for
the heading record.
The following rexx variables and functions are relevant:
- Remove
If this variable is set to any non blank value then
the record will be dropped, the variables value is
shown when debugging so it is recommended that the
value be the reason for dropping the record.
If the contents starts with 'EOF:' then the current
record and ALL following are dropped.
- Column.?
The "Column" array holds the data for each field (that you
are interested in) of the current record in the order you
provided. For example "Column.2" holds the 2nd column's
data.
Note that "Column.0" holds the number of fields in the array.
- Dropped.?
The "Dropped" array holds the data for each field (that you
dropped) of the current record in the order that they were
dropped. For example "Dropped.1" holds the first dropped
field.
Note that "Dropped.0" holds the number of fields in
the array.
- ThisRecordsCodes
This variable gets initialized for each record with the
value that you defined (or allowed to default) for the
"DefineName_RECORD"
option. You can add to or modify this record in any way.
The value of "{$Column1}" gets replaced with the contents
of the rexx variable "Column.1" etc.
If all your records are processed the same way then you
should not need to modify this variable. It is useful where
you might want the output (row of table) to look different
depending on the records data. In some cases this can
be better done by updating the rexx "Column.?" array.
If you need multiple lines you can of course use
"<?NewLine>" where required.
- WriteLineToTmpImportFile()
The passed data is written to the output file, any line
feed characters will indicate the end of a line.
- GetMlField()
This routine can be called to obtain the value of a field
(the name of which is passed).
You can access the fields data in a more efficient manner using
the "Column" and "Dropped" arrays however this routine allows you
to access a variable knowing its name.
- RecordFilter
If you don't need to do any more filtering then you can
clear this variable. This will improve performance.
- DefineName_DELIMITER
This is the character(s) that separate the name of a field from
its value.
- DefineName_SEPARATOR
If you continue a field over onto a following line (the continued
line has no field name) then what are the two components "stitched"
together with?
The default is a space.
- DefineName_LINE_COMMENT_CHAR
This is the character that can be used to start a line for
commenting your file. It defaults to the current PPWIZARD line
comment character.
- DefineName_LINE_FILTER
The contents of this variable should be one or more
rexx expressions.
If an expression is supplied for this option then the filter
code will be called for each non comment line found. This allows you
to build extra smarts into the processing of records if you wish
(for example breaking a table into sections.
The following rexx variables are relevant:
- DefineName_PROTECT_START
By default will be set to the value
<?ProtectFromPpwStart>.
If you have filter code that wants to generate PPWIZARD commands
then you will need to override this value. Have a look at the
multiple HTML pages
example.
- DefineName_PROTECT_END
By default will be set to the value
<?ProtectFromPpwEnd>.
You should also check out an example of importing a file into
multiple HTML pages based
on the contents of one of the fields.
Example - Multi Line Import
Lets assume you have created a database
(called "WEBLINKS.ML") similar to:
;--- First record ------------------------
Name : Dennis
: Bareis
Email : db0@anz.com
Web Page : www.labyrinth.net.au
Comment : Really good site!
;--- Second record -----------------------
Name: Fredric Bald
Comment: This comment contains LT=< & GT=> characters
Web Page: www.somewhere.com
Email: fred@anz.com
Note that in the above sample data the first "name" field spans two
lines to demonstrate line continuation.
Then you can import the data and convert the email and web addresses
into hypertext links with:
<HTML><BODY>
#DefineRexx ML_RECORD_FILTER
Column.2 = "<A HREF='mailto:" || Column.2 || "'>" || Column.2 || "</A>"
Column.3 = "<A HREF='http://" || Column.3 || "'>" || Column.3 || "</A>"
#DefineRexx
#define ML_DELIMITER :
#import WEBLINKS.ML ML "" "{*,Name}Name" "{*,EMail}Email<BR>Address" "{*,Web Page}http://" "{*,Comment}Comment"
</BODY></HTML>
The following code imports the same database but demonstrates field
reordering (unusual requirement), field dropping (email address is not
required) and requiring all fields to be specified and non-blank:
<HTML><BODY>
#define THIS1_RECORD_FILTER \
Column.2 = "<A HREF='http://" || Column.2 || "'>" || Column.2 || "</A>"
#define THIS1_DELIMITER :
#import WEBLINKS.ML ML "THIS1" "{2,Web Page,required,nonblank}http://" \
"{3,Comment,required,nonblank}Comment" \
"{1,Name,required,nonblank}Name" \
"{*,email}"
</BODY></HTML>
PPWIZARD Manual

Tuesday January 02 2001 at 7:37am