Logon failed. Detail [Database Vendor Code: 1005]

[Former Member]

The application make use of ODBC to connect to Oracle database

The way the reports are produced in the current VB application is by using the following line of codes

cryQueryReport.Connect = ObjAdoConnection.sADOconnectstr

cryQueryReport..SQLQuery = sSQL & sSortString

along the way the application also passes String value to the formular fields defined in the reports by making use of the following line of code

cryQueryReport.Formulas(iFormulanumber) = "TITLE_1 = '" & mrsReportItems("TITLE_1") & "'"

Now the codes have been modified to the following to accommodate the upgrade

If Report2 Then

'open the report

Set MyReport = CrystalReport2

Else

Set MyReport = CrystalReport1

End If

'Crystal Report2 includes fields from 9 different tables

'Crystal Report1 includes fields from 10 different tables

For i = 1 To MyReport.Database.Tables.Count

With MyReport.Database.Tables(i)

Set ConnectionInfo = .ConnectionProperties

.DllName = "crdb_odbc.dll"

ConnectionInfo.DeleteAll

ConnectionInfo.Add "DSN", "DSN Name"

ConnectionInfo.Add "User Id", "User ID"

ConnectionInfo.Add "Password", "Password"

End With

Next i

MyReport.SQLQueryString = sSQL & sSortString

For intCounter = 1 To MyReport.FormulaFields.Count

If MyReport.FormulaFields(intCounter).FormulaFieldName = "TITLE_1" Then

MyReport.FormulaFields(intCounter).Text = mrsReportItems("TITLE_1")

End If

Next intCounter

CrystalActiveXReportViewer1.ReportSource = MyReport

CrystalActiveXReportViewer1.ViewReport

The error message pops up that says Run-time Error '2147189176 (80047e48)' Logon failed. Detail [Database Vendor Code: 1005]

when Ok is clicked, another error message says Run-time Error '214191854 (800473d2)': The remaining text does not appear to be part of the formula.

Could anyone tell me what is wrong with the way the Logon information is coded?

Thank you for your time

[Former Member]

This post is being handled through an open support incident with the Developer Support team.

It appears to be an issue upgrading from an earlier version of Crystal Reports using the old crystl32.ocx to the RDC SDK in Visual Basic 6.0.

Elaine

Edited by: Elaine Dove on Jul 6, 2009 2:47 PM