vb Com object nop longer works when deployed

Results 1 to 2 of 2

Thread: vb Com object nop longer works when deployed

  1. #1
    Join Date
    Dec 1969

    Default vb Com object nop longer works when deployed

    I have a vb com object (dll) that contains all of my database <BR>transactions. I call server.createobject(mydll) in my asp application to get access to the various vb routines that return data from my oracle db.This all works fine on my development machine. To take a stab at deployment, I copied the asp project(thru visual interdev) to my target server and registered my vb dll there also. When I try to call up the asp page from any other machine, I get only one listbox that is hardcoded and all my data that should be returned from the vb dll is not displayed. <BR>I have tried to see if this is a security issue by adding the IUSR_MACHINE user to the admin group and giving it Full Control access to the entire tree on the server where the vb dll lives. (maybe a little overkill!) AND I tried enabling auditing for file and object access - the event log was empty!<BR>ANY SUGGESTIONS WOULD BE GREATLY APPRECIATED!

  2. #2
    Join Date
    Dec 1969

    Default RE: vb Com object nop longer works when deployed

    It sounds vague and sarcastic but isn&#039t. Try to figure out what the exact error is and work from there. When writing VB Dlls I try to test for any possible error conditions that might occur, even when it seems impossible. Any time any condition might screw up your code, test for it and raise an error (via err.raise or whatever). <BR><BR>I can&#039t imagine that there is no error occurring at all even without the above provisions (from my experience you will get errors even if you don&#039t raise them when stuff goes bad), so I assume that maybe you are using On Error Resume Next but not actually checking the error?

Posting Permissions

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