Ok, in the past and on our current version 7 script machines when the data station reaches the end of the file, I script the file being moved to the archive, and the .bds file to be deleted. But now in version 9, with no changes of any substance to the code, BWS is producing multiple .bds files. It seems that as I parse files with more than 999 lines, that additional .bds files are created, and named .bds1 .bds2 .bds3 etc. Has anyone seen this? Can I stop it? I know I can code a new procedure to loop back thru the directory and delete any file with "bds" in its name, but that seems clumsy and will eventually come back to bite me. But I can't leave these files sitting there, users drop files into this directory, and this is making my script look like it is really messy. If there is some slick new data station command that makes BWS clean up after itself I would really like to know what that is. Thanks Roy Hayward Catalyst Application Support Manager GHX 3322 West End Avenue Suite 1000 Nashville, TN 37203 615-279-2752 direct 931-670-0867 home 615-525-6746 cell [EMAIL PROTECTED]
