Joined: 19 Jun 2007
Location: United States
Online Status: Offline
Posts: 432
Posted: 29 Aug 2011 at 8:40am
If you have moved to Win 7 is it 64bit? If so that is likely the problem. Without knowing the datasource, a large number are available only as 32bit only and a real challenge. Anyway, if you have not already excluded this as the issue its worth researching.
I know it was something that challenged me as I made the move to Win 7 and one of the reasons some apps I create are done in XP mode. I also had to have Microsoft help me find the right bit of code to create the 32bit DSN in the 64bit system. To their credit they did help.
Let us know how you resolve the problem, it could be useful to a lot developers.
Joined: 19 Jun 2007
Location: United States
Online Status: Offline
Posts: 432
Posted: 29 Aug 2011 at 8:42am
Oh, one more thing if you are doing all this in VS2010 make sure the target cpu is X86 and not any. That can help VS see the DSN and make it available.
Joined: 25 Aug 2011
Online Status: Offline
Posts: 5
Posted: 19 Jul 2012 at 6:13pm
This issue is resolved.
As soon as you open the report, just run the report irrespective of dsn.By doing this , Crystal report will pick up the dsn from ODBC Administrator.Then you can use Set Datasource Location to point to the current database.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum
IP Logged
