Thank you for the reply, Jeffrey.
Before reading your reply - I had done the following:
1 -Execute SQL task that gets all of the userID's that have attachments present in other tables (result set is a variable)
2 - For Each Loop with an ADO Record set enumerator- populated by the above variable
3 - Inside the FE Loop I have a File System Task that creates each users directory in a designated root folder (parameterised)
4 - Outside of the for each loop I have a Data Flow Task with OLEDB Source (Running pretty much the same query as in the Execute SQL Task in step 1 - with the inclusion of the Binary column to be exported)I have parameterised the query so the file path is built when the query is executed and it is stored as a column in the OLEDB result set.
5 - And export column task takes the binary data from the 'Content' column and exports it to the filepath .
It works, but is very crude. It just creates a load of folders, then spits out the documents to those folders. To be a bit more elegant, I'd like to do the document extraction in the FEL container using the ADO enumerator (Create Folder>Create Document>Loop)
Your suggestion of the script task to populate a variable with the export filepath may be a way forward (using a derived column and an export column task)
I'm not very good at all with C# scripts or VB - I'll have a play and see what I come up with - suggestions, pointers all welcome 🙂
Thank you again.