• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 605
  • Last Modified:

ODBC--call failed Error in SQL Record Set


Hi Guys!

How do I get rid of this "ODBC--call failed." error:
                        Dim BioWebServerConnector
                        Dim BioWebMatch
                        Dim MatchResponse
                        Dim ID
                        
                        Set BioWebServerConnector = CreateObject("BioWeb2Server.Connector")
                        Set BioWebMatch = BioWebServerConnector.Match
                        
                        Set rs = Server.CreateObject("ADODB.Recordset")
                        rs.Open "Biometric_Transactions", cn, adOpenKeyset, adLockPessimistic, adCmdTable
                        rs.AddNew
                        rs("UserID") = Request.Form("User_Logon")
                        rs("VerifyFeature") = BioWebMatch.Decode(Request.Form("VerifyFeature"))
                        rs("SupportedDevice") = Request.Form("SupportedDevice")
                        rs("RemoteAddress") = Request.ServerVariables("REMOTE_ADDR")
                        rs("Approved") = 0
                        rs.Update
                        ID = rs("ID")
                        rs.Close
                        Set rs = Nothing
                        
                        If (ID = NULL) OR (Len(ID) = 0) Then
                              Dim ConnectionString, MySql
                              Dim Conn
                              ConnectionString = "DSN=BioWeb;UID=sa;PWD=Not4U2C;"
                              Set Conn = Server.CreateObject("ADODB.Connection")
                              Conn.Open ConnectionString
                              MySql = "SELECT MAX(ID) AS ID FROM Biometric_Transactions"
                              rs = Conn.Execute(MySql)
                              ID = rs("ID")
                              Conn.Close
                              Set Conn = Nothing
                        End If
                        
                        'My boss was always getting a "BioWeb2Server (0x800A005E) Invalid use of Null" error here
                        'I am now getting an "Error Type: DAO.Field (0x800A0C4A) ODBC--call failed." error here
                        MatchResponse = BioWebMatch.Result(CLng(ID))

How do I get rid of this "ODBC--call failed." error? Both the server and the client are running on the same laptop, with the IUSR account set up with access to the database.

Thanx

Dave
0
dbabbitt
Asked:
dbabbitt
  • 2
  • 2
  • 2
  • +1
1 Solution
 
sforcierCommented:
Verify that the value stored in ID is not null by doing this:

If IsNull(ID) Then
   Response.Write "It's NULL!"
   MatchResponse = ""
Else
   MatchResponse = BioWebMatch.Result(CLng(ID))
End If

If the message "It's NULL!" is displayed, you need look at the code above to determine why (post here for help on that as well).
0
 
alorentzCommented:
You'd think at least you would've used the code we wrote in the last Question to clean up you code!!!  Why don't you start with that....and then see what happens.
0
 
alorentzCommented:
0
Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

 
dbabbittAuthor Commented:
I can run Microsoft Script Debugger on the server - Here's what's in the Command Window:

? ID
184

? CLng(ID)
184

? BioWebMatch.Result(CLng(ID))
ODBC--call failed.
0
 
sforcierCommented:
I did a search for the BioWeb components you're using (to try and find a fix). If I'm looking at the right info, then you're trying to get a fingerprint based security system running. I don't mean this to sound glib, but can't you just contact their technical support? I'd assume that a fingerprint security system is expensive stuff, and I can't imagine paying a lot of money and not getting any support.
0
 
sybeCommented:
>>  "Error Type: DAO.Field (0x800A0C4A) ODBC--call failed."

I hope you are not using DAO, because that is vastly outdated
0
 
dbabbittAuthor Commented:
In the ODBC control panel, I discovered it was not able to log in using the sa account.
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 2
  • 2
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now