No Sorry, I haven't used Crystal. If anybody would know the answer, it would be Kevin Goff. He uses Crystal and is writing a book on reporting solutions. Shoot a message to him.


>Hi John,
>
>Thanks for your reply, but the issue is not with SQL Server - the issue is with Crystal Reports.
>
>When designing reports in crystal you can choose from a number of sources of data (dataset, xml, access, sql server,etc). In the report designer when you point Crystal Reports at a SQL Server database, you can either choose windows authentication or sql authentication: that is how Crystal will access the data when the report is run.
>
>In the Crystal report designer, it seems that if you point to SQL Server using windows authentication, it will not let you pass user/password information to the report being run at runtime, so that you could point it at a particular SQL server (test vs. production for example).
>
>Now that I have figured that "bug" out, it looks like the only way to make the above scenario work, is to re-create the report from scratch (which is what I'm trying to avoid). I'm looking for a way to change the database information (in the crystal report) so that the report uses SQL authentication - without touching anything else
>
>Do you know how to do that?
>
>Thanks,