As an Advancement office IT support, we often need to run scripts to generate files from Banner then load the data from external files to banner. All of these in and out actions have never been done by just one single script, one shot, normally it goes, here is the first version of the file? user review? need adding or removing IDs? more scripts? new file etc.. It could go round and round several times between user and IT. In SUNY New Paltz, take the phonathon as an example, we setup a little application by using our reporting tool (Argos), user can select, click and review the their file, then do the modifications that needed, then get the final file; when file came back, they ftp it to the server, then click and review the file; click button to generate formatted pledge file, run the AGPTLMK Banner process and upload all of the changes to Banner. Now users have all the control about their file, the waiting time between user and IT, user and user is greatly reduced and all of the script is centralized too. We also did the same for new parent load, etc.