>>
>>So far I've got as far as running the report wizard in visual studio 2012 so opne to suggestions. Though I think its going to be running as a scheduled job in SSRS.
>
>OK. In a nutshell, you have to
>
>1) Create the report in Visual Studio (either using the wizard, or starting with a blank report)
>
>2) Deploy the report to a report server
>
>3) Create a subscription to export the report (on a schedule) to a CSV file (or some other format). It does require taking the deployed data source on the report server and supplying stored credentials. A scheduled SSRS job won't run if the data source is simply using windows authentication - you have to supply credentials for the data source for the job to run unattended.

Thanks Kevin thats very helpful.

chatting to one of the developers where I am at the moment he tells me with their layers of authorisation etc it can take up to three weeks to
create or implement changes to a SSRS report. :-(