by Dynamic 4GL Text Editing:
In classic 4GL, we made use of the DBEDIT environmental variable to
let the user choose which ASCII text editor (vi/pico/microemacs) to
use. It seems that D4GL is not DBEDIT-aware.
We had to hardcode a program into the form's attribute fields for each
text field in each form. But, we didn't have to hard code a specific
editor in the form. We added the following to each forms' text field's
attrributes: program=dbeditor
We create a shell script called dbeditor, that consists of the
lines:
DBEDIT=${DBEDIT:-vi}
<esc>[0y
<esc>[1y
The second line brings the unix terminal screen to the front (where <esc>
is ASCII(27))
The third line calls up the user's unix editor of choice (or vi).
The third line lowers the unix terminal screen when the editing session is done.
To make it work, this line must be in TERM's termcap entry:
:hp=\E[0y:rp=\E[1y:
Is there a way to bring the text file we LOCATE via our 4GL program
over from our UNX box to the client PC and use a windows editor (winword?)
to display/add/edit the text and return it back to the Unix box to use
in the subsequent SQL add/update commands?
--
______________________________________________________________________
| Raytheon Engineers & Constructors, Inc. (215) 422-4144 |
| Phila, PA, USA |
| Any opinions I state are my own and not necessarily of my employer |
|____________________________________________________________________|