Thanks, that's roughly what I'd gleaned from the other topics on the issue. The problem I'm likely to have is that getting any change made to the server access will be pretty much impossible and any solution that involves too much messing around to get the results onto a normal Windows networked structure will defeat the purpose of what I'm trying to achieve. I'll contact my Admin and see what they suggest, but it's unlikely to be a solution. At the moment I would export one file as a step in the process, to a Windows network folder away from the SAS environment, then use an Excel VBA code to split it. I want SAS to do this bit for me so that one click will update all of the resulting datasets. The results are used as dataconnections for various user tools that we develop, but we develop and don't want to be spending resource updating data where it can be done automatically. I guess what I'm after is the code behind the 'Export {table} as a Step in Project wizard in in EG, but I've not been able to get to that. If I run the code, then manualy add the Export step that would still save time, but then re-running the code as the data updates will remove the Export steps wouldn't it? Is it possible to add the Export Step to each table as it's created by using code perhaps?
... View more