I have a client that needs some ad-hoc item maintenance utilities in
character mode. I don't want to create a unique program for every
file and item type. That's old school. My goal is to spend my time
making the data useful, not writing utilities to maintain these items.

I'm wondering if anyone has published a utility that allows for
editing items for a specified file, with almost nothing but attribute
numbers and related names and field types (maybe just a dict
reference). D3 has a SCREENS capability but that uses funky
keystrokes and someone might as well use UPdate.

I don't want a full-blown application environment like Boston or
PerSay, just a little item maintenance utility that's a few steps up
from ED/SED/AE.

Thanks.
T

On Feb 25, 7:54*pm, Tony Gravagno <tony_grava... (AT) nospam (DOT) invalid>
wrote:
you wouldn't know anything about 'old school' you arrogant prick

Brian Leach has a freebie called ENTER at

http://www.brianleach.co.uk/pages/freebies.htm

However, it's written for Universe - I don't know how much effort it
would take for D3, etc.

Pickie wrote:
*GASP* Thank you so much Keith. Earlier today I was looking for
Brian's freebie page for BCI.IMPORT but I didn't find a link off of
his blog. Thanks for the link back to his main site. *DUH on me*

I looked at the documentation for ENTER and it reminded me that I had
written something like this for D3 some years ago, except as I recall,
my utility was a code generator that operated off of A/S type dict
items. Holy cow, forgot all about it. I will do what I can to get my
utility into the field and will look at ENTER for non-D3 work.

Thanks again.

If there are other utilities out there, please keep the suggestions
coming. Thanks.

T

On Feb 28, 1:40*am, Tony Gravagno <tony_grava... (AT) nospam (DOT) invalid>
wrote:
Tony,

If it's of any interest I put together a line input subroutine years
ago for the "CDS" GPL warehouse/distribution package I did not have
time to finish. It supports VT100 and Wyse60 emulations for function
key and arrow control. I believe in-prompt masked input was added as
well but it's been so long I'd have to dig out the code and look
again. The last thing I remember working on was raw ANSI support and
it was far from usable.

GlenB