PERFORM with text BLOBS?

> > We have had frustrated users enter large chunks of text into a BLOB field > and expect to see them saved when they exited the field only to sadly learn > that they were NOT in an "Add" or "Update" mode but, in fact, had started > the entry while in the "View" mode.....the entered changes are NOT saved > nor is there any user feedback about the pending disaster! > > Has anyone developed a method to deal with this frustration? > > Is there some PERFORM configuration available that would tag "View"ed text > BLOBS as READ-ONLY so that if you tried to execute ":wq" in vi you, at least, > would get a message saying that you couldn't write to the file. > > Thanks for any advice/help/sympathy! > I sympathize. What would be nice is to have a differenet DBEDIT variable for View vs Add/Update. Then you could set one to 'vi' (or whatnot) and the other to 'view' (vi -R). cheers j. ________________________________________________________________________ Jack Parker - Hewlett Packard, DMD/IS Boise, Idaho, USA jparker@boi.hp.com Currently on loan to PLD/PE ________________________________________________________________________ Outside of a dog a book is a man's best friend. Inside of a dog it's too dark to read. (Groucho Marx) ________________________________________________________________________ Any opinions expressed herein are my own and not those of my employers. ________________________________________________________________________