HP3000-L Archives

March 2001, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Erik Vistica <[log in to unmask]>
Reply To:
Erik Vistica <[log in to unmask]>
Date:
Thu, 22 Mar 2001 17:32:24 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (25 lines)
Jeff Kell wrote:
>
> Taken from another list, but a direct quote, regarding a personnel data
> entry form with "smart" name editing/formatting:
>
> > We have an instructor whose first and last name is legally lower
> > case.
> >
> > How can you force-case in [the personnel form]?
>
> Sometimes when it comes to data editing you're d*mned if you do and
> d*mned if you don't :-)
>
> Jeff Kell

Yikes! Ok, here's another one.

I once worked with a guy that claims he legally changed his last name to
'L*' (no quotes). He would log on to the classic 3000 with HELLO
L*,USER.ACCT and it worked! Seems the edit wasn't there for jobname.
Since UDCs/Programs assumed that MPE had done the data editing already,
they would choke on the L*. So, we asked him if he could please not
exploit the bug and use just alphanumeric instead. Geeze, just when ya
think it's safe to ...

ATOM RSS1 RSS2