improve temp/work table naming
#1 Updated by Eric Faulhaber over 11 years ago
The current naming convention of TempRecordN, where N is a sequential number, is severely limiting. Any change to a temp/work table requires full reconversion, because an incremental conversion restarts the number sequence and causes naming collisions. The names must be persisted in the conversion database for consistency across subsequent, incremental conversion runs.
Also, we should do away with the sequential naming convention altogether and base the names on those used in the 4GL code. Note we will have to deal with the case where the same table structure is named differently across external procedures.