Problem in creating AcCmColor object

[a.ghensi689507]

Hi all, I have a problem vhen trying to set a new layer color from VBA/Excel.
If I use the following code:

Set acLayer = acadDoc.Layers.Add(sTag)
Dim aCol As Object 'I have also tried with AcadAcCmColor
Set aCol = acadApp.GetInterfaceObject("AutoCAD.AcCmColor") 'I have also tried with New AcadAcCmColor
aCol.ColorMethod = acColorMethodByRGB
aCol.ColorIndex = color
acLayer.TrueColor = aCol

I got a "Problem in loading Application" error when I try to create the aCol object.
If I use Early Binding, the error is "Cannot find the specified module".

Autocad (2016) loads fine and it's the only version installed.
acadDoc is the AcadApplication object, sTag is the name of the new layer.

How can i solve this?
Thank you for the attention!

[BlackBox]

If memory serves, you need concatenate "AutoCAD.AcCmColor." and the first two characters of ACADVER sysvar.

Now, I skipped VBA entirely, going from LISP --> .NET, so pseudo code might be something like:

Set acLayer = acadDoc.Layers.Add(sTag)
Dim aCol As AcadAcCmColor
Dim sVer As String = Left(acadDoc.GetVariable("ACADVER"), 2)
Set aCol = acadApp.GetInterfaceObject("AutoCAD.AcCmColor." & sVer)
aCol.ColorMethod = acColorMethodByRGB
aCol.ColorIndex = color
acLayer.TrueColor = aCol

Cheers

[a.ghensi689507]

Thanks BlackBox,
unfortunately this doesn't work, I got the same error.
I previously tried by hardcoding the autacad version, same result.

(BTW: VBA doesn't let you declare and initialize a variable in the same line... very annoying!)

Maybe it's time to move the macro to a .NET plugin and using closedxml to read the excel file!

[BlackBox]

Thanks BlackBox,
unfortunately this doesn't work, I got the same error.
I previously tried by hardcoding the autacad version, same result.

Well, shoot. *kicks dirt*

I saw that you hard-coded, but wasn't sure if you used the correct version as that wasn't included in your OP. For that reason, I offered a VBA kludge that I hoped did what my 'blackout' LISP routine does (it changes any layer to black true color with 0.00 lineweight; I also have one for nested layers)... Curious to know if that LISP will work for you, as if not, perhaps there's a repair needed? *not sure*

(vl-load-com)

(defun c:Blackout (/ *error* acDoc oLayers ss oLayer layers acColor)
  (princ "\rBLACKOUT ")

  (defun *error* (msg)
    (if ss
      (vla-delete ss)
    )
    (if acDoc
      (progn
        (vla-endundomark acDoc)
        (vla-regen acDoc acAllViewports)
      )
    )
    (cond ((not msg))                                                   ; Normal exit
          ((member msg '("Function cancelled" "quit / exit abort")))    ; <esc> or (quit)
          ((princ (strcat " ** Error: " msg " ** ")))
    )                                                                   ; Fatal error, display it
    (princ)
  )

  (if (ssget)
    (progn
      (vla-startundomark
        (setq acDoc (vla-get-activedocument (vlax-get-acad-object)))
      )
      (setq oLayers (vla-get-layers acDoc))
      (vlax-for x (setq ss (vla-get-activeselectionset acDoc))
        (if
          (not
            (vl-position
              (setq oLayer (vla-item oLayers (vla-get-layer x)))
              layers
            )
          )
           (setq layers (cons oLayer layers))
        )
      )

      ;; blackout
      (setq acColor (vla-getinterfaceobject
                          (vlax-get-acad-object)
                          (strcat "AutoCAD.AcCmColor."
                                  (substr (getvar 'acadver) 1 2)
                          )
                        )
          )
      (vla-setrgb acColor 0 0 0)
      
      (foreach oLayer layers
        (vla-put-lineweight oLayer 0)
        (vla-put-truecolor oLayer acColor)
      )
    )
  )
  (*error* nil)
)

(BTW: VBA doesn't let you declare and initialize a variable in the same line... very annoying!)

Thankfully, LISP doesn't require variable declaration... As for .NET, hooray C# (.NET generally), and Auto-Property Initializers! Haha

Maybe it's time to move the macro to a .NET plugin and using closedxml to read the excel file!

I know you're after VBA here, however, this old CSV->Layers LISP routine will get-or-create layers, and set their respective properties.

If you need to quickly convert XLS/XLSx --> CSV, this Right Click Excel to CSV Windows Shell Context Menu might help.

Cheers

[a.ghensi689507]

Thanks BlackBox,
I haven't tried the lisp you posted yet, but I found that the problem occurs only on my colleague's computer that has office 2016 installed. In my computer (Office 2013) everything runs fine using the GetInterfaceObject. Next week I'm going to investigate what is the real culprit an how to solve it!

[Ed Jobe]

I've seen times where installing Office after Autocad messes up Autocad's vba. The solution was to reinstall autocad vba.