Your DBA is right. I would create a table with a lot months e.g. like your DBA 60 months. Each column is one month from year1, month 1 to year n, month m(=12). For your convenience views may be created. One view contains 24 months and the first view starts in year 2, month m-1 and the last view ends with the months year n-1,month m. The number of views is (n-2)*m+1. This is a lot of work for DBA. If your DBA is following a strict naming rule and you are allowed to create ORACLE views you may write a macro to create a temporary ORACLE view containing the columns you want to read. In this case the DBA must only fill the ORACLE table. No permanent ORACLE views are needed.

--------------------------- Andreas Grueninger PRIVATE: grueni@stuttgart.netsurf.de OFFICE: grueninger@lfl.bwl.de ---------------------------