hexagon logo
Register Sign in
  • Replies 25 replies
  • Subscribers 31 subscribers
  • Views 349 views
  • Users 0 members are here
Options
Related

Need help with VB6 .Net

DJAMS
Upgraded my workstation to Windows 10, so VB6 is no longer an option for my PC-DMIS software efforts.

I've got Visual Studio 2107 now, and I've run into a problem using PC-DMIS collections. In a nutshell, vb6 .net doesn't recognize them as collections. I have to declare the PC-DMIS application as "Object" in order to be able to enumerate through the collections. I was told that this means it's doing "late binding" - who cares. I need intellisense because I'm a terrible typist. In the screenshot below, if I change the declaration of the "app" variable to type "Object", the compile error goes away, and the code runs fine. But I don't see this as a solution.

I'll also point out that the Microsoft's File System Object collections work just fine when used in the same manner.

Has anyone got the solution to this problem?


Parents
  • Made me look in mine. Doesn't work. Check mine out.. 

    Dim app As PCDLRN.Application
Dim cmds As Object
Dim cmd As PCDLRN.Command
Dim part As PCDLRN.PartProgram

    Then go ahead and use this 
    For Each cmd In cmds


    Intellisense pops up with '.Commands' but bombs out during execution yet it's OK with".Command". Weird.

    It's the exact same problem I'm having, you're just getting there a different route. You've got cmds declared as Object, when it should be declared PCDLRN.Commands. I've got a bad feeling that this is a problem with the way all of the pc-dmis collections are setup. Hoping like crazy that I'm wrong, and there's just something that I don't know.
Reply
  • Made me look in mine. Doesn't work. Check mine out.. 

    Dim app As PCDLRN.Application
Dim cmds As Object
Dim cmd As PCDLRN.Command
Dim part As PCDLRN.PartProgram

    Then go ahead and use this 
    For Each cmd In cmds


    Intellisense pops up with '.Commands' but bombs out during execution yet it's OK with".Command". Weird.

    It's the exact same problem I'm having, you're just getting there a different route. You've got cmds declared as Object, when it should be declared PCDLRN.Commands. I've got a bad feeling that this is a problem with the way all of the pc-dmis collections are setup. Hoping like crazy that I'm wrong, and there's just something that I don't know.
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement