ActiveWorkbook.VBProject VBComponents

[drom]

Thanks in advance!

I already know this web:

http://www.cpearson.com/excel/vbe.aspx

I have checked the following reference whithin Excel VBA's references Manually:

Microsoft Visual Basic for Applications Extensibility 5.3


BUT when I run the following Macro, once checked the prior reference:

Sub AddModuleToProject()
  On Error Resume Next
      Debug.Print Err           ' I GET 0
Dim VBProj As VBIDE.VBProject:      Set VBProj = ActiveWorkbook.VBProject
      Debug.Print Err           ' I GET 1004
Dim VBComp As VBIDE.VBComponent:    Set VBComp = VBProj.VBComponents.Add(vbext_ct_StdModule)
      Debug.Print Err           ' I GET 91
    VBComp.Name = "NewModule"
      Debug.Print Err           ' I GET 91
End Sub

Why I get those errors.

What am I Missing??

 

[xld]

I have used that code and I don't get those errors.

 

[drom]

I have been using code like this for a big while in my office.

not at home.

In my office I don't get any err


At home YES.


this is the reason Why I am asking what am I missing

Thanks!

 

[mikerickson]

Is the Microsoft Visual Basic for Applications Extensibility library active in the erroring environment?

If not, dimming the variables as Object might set things right.

 

[drom]

Is the Microsoft Visual Basic for Applications Extensibility library active in the erroring environment?

If not, dimming the variables as Object might set things right.

Is the Microsoft Visual Basic for Applications Extensibility library active? YEs it is active, Checked.

in the erroring environment? Don't know what you mean

I run the macro after checking the reference first.

 

[mikerickson]

By "in the erroring environment", I meant at home, where you get the errror. At work, it looks like the library is active.

 

[drom]

By "in the erroring environment", I meant at home, where you get the errror. At work, it looks like the library is active.

In both places at home and in my office the reference is active!

so, I don't understant?

Thanks!

 

[mikerickson]

It worked on my machine without error.
Have you tried dimming VBComp as Object?

 

[Norie]

Have you tried specifying the workbook explicitly rather than using ActiveWorkbook?

 

[xld]

Do you have Trusted Acc ess to VBA projects set? This would be my guess.

Is the project password protected?