Thanks Ludek. I will keep this in mind in the future. I ended resolving my issue by change the Provider for my datasoure from "SQLNC11" to "SQLOLEDB". That resolved my issue. However, I will look into changing our code to be similiar to what you suggested. I think it will prevent further headaches in the future. We do not have a great separate dev environment. So we are oftend copying reports around and changing the datasource for dev / testing purposes and then changing back to production. If I am reading your response correct, this activity will cause issues using "SetDatabaseLogon" and that using ApplyLogOnIfno will be the best method. Am I understanding you correctly?
thanks
doug