Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. Visual Basic
  4. COM Exception in VB6 to VB.NET conversion [modified]

COM Exception in VB6 to VB.NET conversion [modified]

Scheduled Pinned Locked Moved Visual Basic
helpcsharpcomtutorial
1 Posts 1 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • B Offline
    B Offline
    BREdwards
    wrote on last edited by
    #1

    Hello, I'm in the process of converting an application from VB6 to VB.NET. So far things have been going very smoothly, however I've come across an error I'm not sure how to get around. It happens on a line with a function that takes an object as its argument and returns a short. Basically what's supposed to happen is that if the result is not -1 then the app is supposed to close out due to it timing out if a button isn't clicked in time. So far, after stepping through, the aforementioned function seems to run without error, but when the app tries to compare the result against a constant (-1), then the error occurs. The error is this: Error Code 61837 Error Source is something I'm not sure how to duplicate with a keyboard, looks like 8 to the first power and a capital A with a tilde over it. Error message is "Unable to write read-only property" Here's the line in question: If util_Pause(myObject.Property, 200) <> CONST_MINUSONE Then Thanks in advance [EDIT] Okay, I fixed the issue, though any advice for the future would be welcome. I just set an object variable equal to what I was originally throwing into the function and just threw that in as the argument. That fixed the issue.

    modified on Friday, March 20, 2009 8:57 AM

    1 Reply Last reply
    0
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • World
    • Users
    • Groups