Sounds very strange!
Is your source query just a 'standard' SQL command or is it derived from a variable and/or expression? Is the SSIS package running as a SQL Agent job or are you manually executing the package either in Design or Run mode? Is the data time-dependent in any way?
Have you tried running a Profiler trace to check that the target database is being accessed by the query?
I had to set this issue off to the side, but I'll have to solve this one soon.
It's a straight-forward SQL query, but I do build it into a SSIS variable. I could put a message box in a script task to display the query string -- that's a good thought.
I am manually running the package through BIDs.
Not time dependent.
The profiler suggestion is a good one as well.
Thanks for the suggestions, I'll post back what I find.