How did you set the destination? Any config or variables involved?Arthur My Blog

The destination is set by concatenating these together. [Output Folder Path] from the DTSCONFIG file. [FileName] variable generated from the BLOB row's Primary Key (e.g., File_Upload_ID_123.mdb). Then, I perform a SELECT from my OLE DB Source to feed into the Export Column Transformation. SELECT @[User:OutputFolderPath] + @[User:FileName] as [OutputFilePath] ,[FileBlob] FROM dbo.MyTable Please let me know if you need any other details. I appreciate your help looking into this.

Hello, I hope someone can help me troubleshoot this strange behavior between my Development v.s Deployment environments. My SSIS package exports a BLOB column===>a physical Microsoft Access .mdb file using the Export Column Transformation. Executing the SSIS package inside BIDS 2008 (Business Intelligence Development Studio) exports the BLOB column to a physical .mdb file. Afterwards, I am able to open the MDB file using Microsoft Access 2010 successfully. Then, I deployed my SSIS to a Windows Server 2008 64-bit with SQL Server 2008 R2 64-bit. Executing my SSIS package creates the .mdb file. However, Microsoft Access keeps displaying the "Unrecognized database format" error message dialog every time I open it. Opening the .MDB file in Notepad and this is the file content. "The original file is in the temp folder. Full path of the file: C:\Temp\abfb9806-c06e-4b5f-9713-1388821a3e83.tmp" No "C:\Temp" folder exists in my C: drive. Obviously this C:\Temp\abfb9806-c06e-4b5f-9713-1388821a3e83.tmp file does not exist at all. It works perfectly fine in my Development machine. But the file doesn't get written out properly in my Deployment environment. So can anyone please give me some ideas why it is not working? Thanks in advance guys :-)

My bad...I trusted that the data in my deployment environment was valid. Whoever uploaded the BLOB into the deployment environment didn't do it properly and that is why I was getting an error. My code works fine.