+1  A: 

Contains youir connectionstring the option 'MultipleActiveResultSets=True'? If yes, try to remove it and look at sql profiler.

Olaf Tinnemeyer
Yes, the work-around of changing the *MultipleActiveResultSets* option within the connection string from the default of True to False instead, causes Profiler to properly report the query executing in the application database.Sounds like a bug to me, but I can live with this work-around. **THANKS!!!**
AjarnMark