on 2009 Aug 26 6:37 AM
Which is better to use ODBC Connection(System DSN) or OLEDB? In our experience, we are using oledb connection, but our problem is if our server name or server port change we are obliged to recompile reports. in our application at runtime we are also passing oledb connection parameters.
For example we compile the reports using stldev as server name and port is 7000. In our application at runtime we also pass this connection parameters: stldev as server name and port is 7000. Now we notice that if at runtime we pass a different connection parameters lets say stldev as server name and port is 8000 we notice that loading of reports slows down.
Now I'm thinking of using ODBC System DSN instead. does it worth it?
Hello,
The best person to determine the better way is you in your own testing.
Does the ODBC driver work more efficiently in your case?
It may also depend on the version of Crystal Reports you are using and the Service Pack involved. There may be updates to the drivers you are using that may enhance their performance or to fix a known issue.
You do not say what version of Crystal Reports you are using, what type of database and the version or what SDK you are using in your application.
It would be difficult to give you a more detailed answer without that information.
Elaine
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
62 | |
12 | |
7 | |
7 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.