1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
|
.TH gdbload 1 "February 1996" "Steve Roth et.al." "HP100LX Tools"
.SH NAME
gdbload \- load ASCII formatted data into an HP 100LX database
.SH SYNOPSIS
.B gdbload
.RB [ -an ]
.I database
[
.I input
]
.SH DESCRIPTION
.B gdbload
loads ASCII formatted data into an HP 100LX database.
.I database
is the name of the 100LX database to modify.
.I input
is the name of a file of ASCII data to load into the database.
If no input file is specified, the standard input is used.
The ASCII file format is one exported by many database packages as
well as by
.IR gdbdump (1).
.SS Options
.B gdbload
recognizes the following options:
.RS
.TP
.B -a
Add the records from the ASCII file to the database, keeping the records
already present in the database. By default, the records in the ASCII
file replace those already in the database.
.TP
.B -n
Do not back up the database file. By default, the original, unmodified
database file is left in a file with the same name and a .bak extension.
.RE
.SS "Input Format Description"
The input to this program is an ASCII text file which starts with a line
containing field names. This line indicates the order in which fields appear
on subsequent lines. Not all fields of the database need be specified;
unspecified fields will be left blank in all added records. Field names
are not case distinct and ampersands (&) are ignored in comparing field
names.
.PP
This first line is followed by one line for each record of the database.
Note that any of these lines may be split into multiple lines if
needed, by placing a backslash (\\) at the ends of lines which are continued.
Also note that string fields may span multiple lines provided they are quoted.
Apart from line splitting according to these rules,
each "logical" line contains all of the fields
whose names were listed on the first
line, in the same order as on the first line.
The fields (and the field names, on the first line) are separated by commas.
.PP
Exactly how each field should appear depends on its type.
Text fields, category fields, number fields, and note fields should
have their text quoted if it contains commas or newlines.
The following escape sequences are understood:
.RS
. Can't produce a \ on Solaris nroff, need to manually substitute \ for % !
. We can produce a \ using groff though...
.TP
.B "\er"
Carriage return (ASCII 13).
.TP
.B "\en"
Line feed (ASCII 10).
.TP
.B "\ennn"
nnn are octal digits representing a character.
.TP
.B "\exnn"
nn are hexadecimal digits representing a character.
.RE
.PP
Any other character following a backslash is treated as a standard
character with no special meaning, i.e., backslash and quote marks can
be escaped by preceding them with a backslash.
.PP
Date fields should appear in the format YYYYMMDD;
for example, August 15, 1993 should appear as
19930815. Time fields appear in the format HHMM, where HH is in the
range 00-23. Date and time fields may also be left blank, i.e.,
nothing between the commas.
.PP
Radio buttons and check boxes are turned off if the field is empty or
contains a 0; they are turned on otherwise.
.PP
No other field types, including application-defined types, are accepted
by
.B gdbload.
.PP
The output from
.IR gdbdump (1)
matches this input format, unless the
.B -n
flag is given to
.IR gdbdump (1).
.SH WARNINGS
When the newly constructed database is first opened by the 100LX,
it will (erroneously) be reported as being empty. This is because
.B gdbload
does not construct database indexes, and the 100LX expects the index for
the current "subset" to be valid. The situation is remedied by pressing
F6 and selecting any "subset" (even the current one!) This will rebuild the
index for that "subset", causing records to display normally. The delay
caused by the rebuild depends on the size of the database (among other things),
and ranges from imperceptible for small databases up to several minutes.
This delay will occur whenever a new "subset" is selected for the first time.
.PP
.B gdbload
will not attempt to modify HP 100LX
Appointment Book and World Time databases.
.PP
.B gdbload
will not allow you to specify data for application-defined fields of a
database.
.PP
This program cannot handle password-protected databases. Attempts to
load data into password-protected databases will have unpredictable results.
.SH AUTHOR
.B gdbload
was written by Steven Roth, stever@cup.hp.com, and is being maintained
by Arne Christensen, arc@pine.dk. Contact the latter
for bug reports, enhancement requests, or to get a copy of the source
code.
.SH DISCLAIMER
This program is released into the public domain and
neither the author nor the maintainer place any restrictions on its use.
We make no warranties or guarantees for this program and
you use it at your own risk.
This program is supplied by us personally and
not by Hewlett-Packard Co. or Pine Tree Systems, which incur no
obligations pertaining to it.
.SH ACKNOWLEDGEMENTS
Many thanks to Andy Gryc for publishing the details of the database file
formats!
.SH SEE ALSO
gdbdump(1).
|
