I would like to throw something else into the mix.  How would native mode KSAM files fit in.  I have a third party payroll system that uses NM KSAM files as the database rather than IMAGE.  We have been debating which is the best way for users to access payroll/HR data from this system for both reporting and inquiry purposes. One school of thought is to create a DW by extracting data from the Payroll System using tools provided by the vendor. The problem with this, for us at least, is that payroll data is constantly being updated to the KSAM database through the third party package and users want up to date info.  So the DW concept,  is not the best way to go for us. 

        My other thought is to use ODBC to connect directly with the KSAM database and create a client server front end with something like Visual Basic.  This way there would be dynamic access to the KSAM database and the users would be happy.  There must be trade off's.

        I would like to hear from some of you regarding your experiences and opinions.

        By the way these KSAM files are very large, approaching the 4gig limit and we run on a 3k 987sx.  No problems with CPU utilization or disk space.  This box hax 1.5 gig of memory so at this point the system is quite stable.  But what would happen if I add an Image database for the DW.

        Thanks in advance

        Lets keep this thread going!

        Jack Calandra
        System Manager
        AIG HRIS