This week I was involved in a project where we needed to implement a small reporting mechanism. As we are using Visual Studio 2005 and Crystal Reports was handy, since it was tightly integrated, we decided to implement some reports with it. Everything went prety fine until the moment of setting the report logon info at runtime. The headakes started.
From my experience i have come to the following conclusions:
- If you create a database connection with Integrated Security, no matter what you do, you will never able to switch, at runtime, to SQL Security.
- You cannot change the initial server and database name, as well as the user id and password.
Since I could not find any suitable workaround for this problems, I have decided to install the Crystal Reports XI full product and implement a new report from scratch.
Happily everything works fine now, or at least I hope so.
This behavior is absolutly unaceptable in a develoment tool such as the MS Visual Studio 2005. I let this tips for you guys hopping that you don’t spare your precious time.
April 5, 2007 at 11:58 am |
Yes you are correct..
I had also same problem. After that i removed the crystal report 10.0 dlls and replaced with 9.2 dlls. Now it’s working fine.
I dont know whether its correct method. I have analized more time and spent nearly 3 to 4 days for this.
Thanks for ur info