I can't get an answer from Seagate as my problem is similar. I have native (DSN-less) reports that I have deployed (as I thought this would be easier to deploy). On testing them in my development area I have no problem at all and changing the locations and connections in code isn't a problem...
The one thing you cannot change in the Crystal Report is the Server Type. If the report is originally setup to use ODBC it cannot be changed to a DSN-less connection. The report must be changed to be Native connection and then the server type will change from 'ODBC - DSNName' to the database Server.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.