Results 1 to 4 of 4

Thread: Updating COM Components

  1. #1

    Thread Starter
    Addicted Member Gavin_Mannion's Avatar
    Join Date
    Aug 2001
    Location
    London, UK
    Posts
    214

    Updating COM Components

    Hi All,

    I have been given the task of debugging a few COM Components which are running as part of a large ASP application.

    I have edited the source code and created myself a new .dll, I have then gone to the server, unregistered there .DLL and registered mine. But as soon as I try and use the component the web application crashes with no error message. I just get the error page 500.100?

    Can someone let me know if there is something I am missing, I have never used these COM components before.
    Gavin Mannion

    Jackofalltrades.

    "Some people are alive simply because it is against the law to kill them." - Anonymous

    //TODO: Insert smart comment here

  2. #2
    PowerPoster Lethal's Avatar
    Join Date
    Oct 2000
    Location
    Ohio
    Posts
    2,496
    When your ASP page tries to instanciate an object from your component, you may have changed the Prog ID of your component. Make sure the ProgID in your ASP page matches up to the ProjectName.ClassName of your class.

    Code:
       ' In Your ASP Page
       Set objX = CreateObject(ProgID Goes Here)

  3. #3

    Thread Starter
    Addicted Member Gavin_Mannion's Avatar
    Join Date
    Aug 2001
    Location
    London, UK
    Posts
    214
    The only thing that I can see different is that I do not have the Set word in front of my CreateObject.
    If I put it there I get this error message.
    =====================
    Microsoft VBScript runtime (0x800A01A8)
    Object required: 'Server.CreateObject(...).ReturnAccountDetails(...)'
    =====================
    In my Login.asp page I have the following
    Code:
    gReturn = Server.CreateObject( _
                                     "CaseManagement.AccountConnector" _
                                      ).ReturnAccountDetails( _
    			gstrConnection, _
    			gstrAccountName, _
    			mstrPassword, _
    			mlngAuthorityLevel, _
    			mlngPasswordAge)
    My Project name is 'CaseManagement.vbp'
    My Class Name is 'AccountConnector'
    And my function is
    Code:
    Public Function ReturnAccountDetails( _
                        ByVal ConnectionString As String, _
                        ByVal UserID As String, _
                        ByVal Password As String, _
                        ByRef AuthorityLevel As Variant, _
                        ByRef PasswordAge As Variant _
                        ) As Long
    As far as I can see everything looks 100%.

    Is it possible that they have not given me the original project and that is why this is not working?

    Thanks
    Last edited by Gavin_Mannion; Feb 21st, 2002 at 04:06 AM.
    Gavin Mannion

    Jackofalltrades.

    "Some people are alive simply because it is against the law to kill them." - Anonymous

    //TODO: Insert smart comment here

  4. #4
    pvb
    Guest
    uh, you can't do that kinda stuff with vb6:
    Code:
    Set myObj = Server.CreateObject(progid).CallSomeMethod
    try this:
    Code:
    Dim oMyObj
    Set oMyObj = Server.CreateObject("CaseManagement.AccountConnector")
    gReturn = oMyObj.ReturnAccountDetails(gstrConnection, _
     gstrAccountName, mstrPassword, mlngAuthorityLevelk, _
     mlngPasswordAge)
    Set oMyObj = Nothing

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width