How to deal with variable table names in 4gl
Posted in 1991
From what I understand, this is not easily doable. Case statements in the code are not acceptable, as the table names will be generated by the program. The exact problem in this case is wanting to split transaction files into monthly files so they can be archived (automatically on an Epoch Infinite Storage Server) on optical disk. However, the current year and maybe even more needs to be easily accessible to 4gl programs. How is this for a solution: every month, run a ESQL/C program which renames the table CURMONTH to APR91 (there would have to be more info in the names, but you get the idea) and changes a set of views which are unions of the current month and however many months you want in the past. I realize this would be readonly, but that is not a problem since updates would only occur in CURMONTH. The reason for all this is that the Epoch only moves files to/from optical storage on a per file basis -- ie, you can't archive part of a file. Any comments or other suggestions would be appreciated. John Tamplin Xavax jat@xavax.COM 2104 West Ferry Way ...!uunet!xavax!jat Huntsville, AL 35801