Can someone please explain the difference between Native and ODBC Connections?
A recent issue that I had calling a Stored Procedure that executes a database Update, required changing to the Native connection instead of the ODBC to get around a Read-Only Transaction error.
I was told to specify a native connection you must browse to Create New Connection via Std Rpt Creation Wizard, specify Oracle and then setup the Service, user, etc.
Is there a way to save this (locally, repository, etc) so other report creators do not have to go through this process for each report they create?
I know it is not many steps, but to some it is confusing and they originally had wanted us to all just select from the ODBC connections in the My Connections section at the top of the Std Rpt Creation Wizard.
Perhaps I just do not understand the nature of native versus ODBC but it would be nice to be able to add native connection definitions to the list of available connections so they remain available. Perhaps they are and I just don't know it. Our ODBC connections use the same name as the TNSNAMES 'service' so maybe that is why I am confused.
I appreciate any light that can be shed on native connections, etc. and/or references that can be provided.
Thanks,
Bill
Edited by statey603 - 23 Aug 2013 at 4:55am