RE: Re: worst RPG ever seen?

[rob@xxxxxxxxx]

I've seen character fields used as keys, but limited to digits for new 
data entry.  Here's the thought process.  "We want people using our 
software to be limited to numerically generated keys.  However, we want to 
make an easy transition for people to migrate to our software from their 
existing package.  Their existing package may have characters allowed." So 
any custom file conversion to migrate from package xyz to their package 
would move the old alphanumeric key in there.  Any new keys generated 
would be numeric.  Some area's of SYSGEN/INTEGRAL/SOFTWARE 
PLUS/UNICORN/whatever their name-of-the-day is, do this.  But they don't 
tend to mix and match from one file to another.  They even keep the same 
field names.  If the key is called EMPNO in one file it will be called 
EMPNO in another.  Why pervert the database to accommodate RPG 
limitations?

Many of these queries can be resolved with a decent logical file, or view, 
instead of having to duplicate this effort anytime you create a new query.

Rob Berendt