Skip to Content

Connectivity Issue

This is a post on behalf of Mr. Zdenek Vykipal:

" Problems porting 32-bit Crystal reports from ODBC to 32-bit ADO provider for Oracle - getting "Log on failed" exception.

I used code examples from the web to load a report from file, create ConnectionInfo and assign the new connection information to the tables and sub-reports.

Upon return from the failed login attempt ("Log on failed" message), the new log on dialog displays the original ODBC values in the Server Name and Database fields. It is worth noting that I am able to create working x86 applications using the Oracle.DataAccess.dll.

Thanks for your help.

Best,

Den "

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Best Answer
    Posted on Nov 12, 2015 at 06:29 PM

    When changing from ODBC to OLEDB (ADO), you have to also set the database driver when you set the connection.

    However, the version of the driver may also be an issue. Crystal can be picky about how it connects to Oracle. If at all possible, I always use Crystal's "Native Oracle" connection. It's faster, more stable, and allows you to leverage more features from Oracle in things like SQL Expressions and Commands.

    -Dell

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.