RickThompson
Programmer
This error is really stumping me!
Below is a code snippet, showing the essential features of the code that's eating my lunch....
Each time I call this, it fails immediately upon the call to the function. Debugging shows me that it gets beyond the declaration of objcls. The argument list is all correct (and would generate a different error, anyway). All strings are passed to the function BYVAL.
This is the code that runs on the client system. In this, BCaller_DVLP is the component linked to the client PC, that acts as the 'gateway' to the other mid-tier components and functions. In the dozens of function calls that BCaller_Dvlp handles, this is currently the only one that fails like this. Running the app, objects created in functions just prior to this work just fine.
The error # that's returned is -2431937333 (or something equally bogus). This is, in my experience, indicative of an inability to connect to the component being called. However, the object creation worked just fine, and other functions connect to it without problem.
This example shows the object in use WITHOUT an OBJECTCONTEXT object. I have also tried it using an object context, and get the dreaded '91' error.
Any help or suggestions would be GREATLY appreciated.
=====================================
Private Sub cmdVacant_Click()
On Error GoTo EndTrans
Dim objcls As Object
Dim blnReturn As Boolean
Set objcls = CreateObject("BCaller_Dvlp.clsBCaller"
blnReturn = objcls.SaveCrewSlotsVacant(lngCrewSlotID, _
lngEmployeeID, _
strError, _
strCurrUser, _
bteSecLevel )
Select Case blnReturn
[other stuff]
End Select
Set objcls = Nothing
Exit Sub
EndTrans:
Set objcls = Nothing
MsgBox "Error in cmdVacantClick: " & Err.Number & " " & Err.Description
End Sub
=============================
[sig][/sig]
Below is a code snippet, showing the essential features of the code that's eating my lunch....
Each time I call this, it fails immediately upon the call to the function. Debugging shows me that it gets beyond the declaration of objcls. The argument list is all correct (and would generate a different error, anyway). All strings are passed to the function BYVAL.
This is the code that runs on the client system. In this, BCaller_DVLP is the component linked to the client PC, that acts as the 'gateway' to the other mid-tier components and functions. In the dozens of function calls that BCaller_Dvlp handles, this is currently the only one that fails like this. Running the app, objects created in functions just prior to this work just fine.
The error # that's returned is -2431937333 (or something equally bogus). This is, in my experience, indicative of an inability to connect to the component being called. However, the object creation worked just fine, and other functions connect to it without problem.
This example shows the object in use WITHOUT an OBJECTCONTEXT object. I have also tried it using an object context, and get the dreaded '91' error.
Any help or suggestions would be GREATLY appreciated.
=====================================
Private Sub cmdVacant_Click()
On Error GoTo EndTrans
Dim objcls As Object
Dim blnReturn As Boolean
Set objcls = CreateObject("BCaller_Dvlp.clsBCaller"
blnReturn = objcls.SaveCrewSlotsVacant(lngCrewSlotID, _
lngEmployeeID, _
strError, _
strCurrUser, _
bteSecLevel )
Select Case blnReturn
[other stuff]
End Select
Set objcls = Nothing
Exit Sub
EndTrans:
Set objcls = Nothing
MsgBox "Error in cmdVacantClick: " & Err.Number & " " & Err.Description
End Sub
=============================
[sig][/sig]