I have several legacy Access 2003 and 2007 databases. I am trying to use seven of them as sources for an SSIS routine that runs at 1 AM and consolidates them into a single SQL Server 2008 R2 table. The SSIS routine is fine. But...it dies after 2 seconds with an error message that the Access databases have locks on them. We have conducted tests where all users have exited Access and shut down for the night. But the SSIS routine continues to reflect the "locked" problem. I am not seeing any .ldb files where the Access files reside (on a server). Is there any way of freeing up these phantom "locks" so that SSIS can run without corrupting the Acess databases? Thanks. ===

Since your issue appears to be related to SSIS, I am going to move your thread to the SQL Server Integration Services forum. Best Regards, Nathan Ost Microsoft Online Community SupportPlease remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

This is a duplicate of http://social.msdn.microsoft.com/Forums/en-US/sqldataaccess/thread/fc738d72-2db0-4392-a5a1-7f358cb2878d/Jeff Wharton MSysDev (C.Sturt), MDbDsgnMgt (C.Sturt), MCT, MCPD, MCITP, MCDBA Blog: Mr. Wharty's Ramblings MC ID: Microsoft Transcript Please mark solved if I've answered your question, vote for it as helpful to help other user's find a solution quicker

include a file task and make a shadow copy of the access database and then hit it it should work fine and it will even avoid corruption of data