LK>Our file naming schema is based on the client matter.  We have a
LK>three-part client matter number.  It starts with a 4-6 alpha client
LK>acronym, followed 1-digit number (1-8) depending on the nature of the
LK>file, and then a 5-digit unique matter number.  Therefore, a if I
LK>were to have a file opened for me on a U.S. patent issue, it might be
LK>something like this: 
LK>    LARK-1-13500
Lawrence--
   That sounds *very* complicated, and a system that would take awhile 
to learn (i.e., memorize) so that one does not have to constantly look 
up the various codes, etc. Although I may need to get to such a 
sophisticated system at some time, it seems like "overkill" now. 
   Any thoughts about a simpler solution that would be easier to 
remember and implement?
LK>This is all handled quite automatically and very much behind the
LK>scenes. 
   Would you mind explaining how it is handed "automatically" and 
"behind the scenes"?
   Lawrence, thanks for taking the time to reply.
Regards, --Barry
--- FLAME v1.1
---------------