     ID_Numbers:
ID_Numbers are the 2nd index, (Group being the first).  If you 
decide to number your own, use any # between 1 & 1 million, or > than
1 Billion (see below).  We have reserved from 1 million to 1 Billion
for our own standardized KSAs.  If you leave Id_Num field blank (which
we recommend that you do, just because it is easier) then ID_Numbers
will get auto filled (on exit & save) by hashing attempts, starting at 1.
Likewise if the user accidentally assigns duplicate keys to 2 different
records, then a keyviolation module hashes the duplicate record in, 
assigning it a different ID_Number.

If you are a small company, you may wish to set up a KSA group-ing
scheme using dual indices (Group, then ID_Number.  Company Personnel
Departments may wish to do this with their own KSA's. 
Updates to the KSA_Long (Standardized KSA's) file are handled semi-
automatically and maintained by UPSC.  All the user has to do is to
download all the UJA_KSA.zip & UJA_KSAL.zip files from all the months
between now & when he bought the package, & copy them to the installed
UJA directory.  Then he has to take the ADD_UJA (L) menu options.
New Adds, Deletes, & Changes are automatically handled by the program.
Short KSAs [70 wide's] are auto sorted alphabetically, & thus
have no separate INDEX field, so you cannot assign them to groups.


Any user additions to Id_Numbers > 1 million will  cause our updates 
(when you take the KSAs_STANDARD APPLY KSALs Menu Option) to wipe out 
the users additions.  We have chosen to  permanently assign Id_Numbers
> 1 million so the user can refer to long  KSAs by a number, otherwise
he would have to use record no. (which  changes all the time, or quote
the string.  
If you are a large corporation or govt agency and you want to be
able to use ID_Numbers > 1 million, then dont apply any of our KSA
updates, or number your KSAs high enough (you can go up to 12 
digits) to avoid ours, & apply our KSAs, which will start out 
at 1 million & go up from there as we get in new KSAs from the user base.
Thus corporate KSAs in the range of 1 Billion on up should virtually
be safe from our overwrites until Judgment Day, when you will no
longer need KSA's or Job Apps.  Somewhere after 1 billion & before 1 
trillion, Paradox 3.5 expresses the number in exponential form on 
reports, & forms, so if you dont like exponential notation, that is
a factor.

APPLY KSAL's Menu Option allows you to update the KSA file with the
latest reported KSA's.  Download this zip file (called UJA_KSAL.zip)
from any one of the Current version BBS's, e.g. America Online,
CompuServe, our BBS, or the InterNet, etc.  Once you have it
downloaded, copy it to your UJA directory, unzip it, & delete the
zipped version.  You will be left with a file called UJA_KSAL.DB. 
UPSC will update it's list of KSA's periodically (monthly, or so) to
incorporate the latest ones reported by users.  We appreciate your
input to keep us abreast of technology's ever changing KSA's.
E-mail a note to us & the text file that is generated by the Main Menu
option Extract KSAs.
