Runtime Error '1004' - but different

Hi,

I am a newby to VBA and copied a VBA macro to my Excel to test.

The PARTIAL code is:

Sub MakeUserForm()
    Dim TempForm As Object
    Dim NewButton As MSForms.commandbutton
    Dim NewLabel As MSForms.Label
    Dim NewTextBox As MSForms.TextBox
    Dim NewOptionButton As MSForms.OptionButton
    Dim NewCheckBox As MSForms.CheckBox
    Dim X As Integer
    Dim Line As Integer
    Dim MyScript(4) As String

    'This is to stop screen flashing while creating form
    Application.VBE.MainWindow.Visible = False

Now, I run this and get a runtime error on the last line in this example . I have all the references set according to the directions, but this keeps coming up .

Please help me understand why this happens .

Also, this is posted at Tek-Tips
(http://www.tek-tips.com/viewthread.c...1421046&page=1) but I cannot get anyone to finalize an answer.

P.S. The code is at http://www.tek-tips.com/faqs.cfm?fid=5757 and was from Wallenbach originally - per the post.

Thanks
E

Try

Application.ScreenUpdating= False

as an alternative.

Is the VBIDE library open?
I think that the VBEditor.MainWindow is only avaliable through the VBIDE.

From the VBEditor Tools menu> References, the
Microsoft Visual Basic for Application Extensibility library should be open.

(This is from memory, a slightly different name may be what you see.)

OK, tried the Application.ScreenUpdating = False. Did not work. Well, did get past this but still getting an error on the next line which also has to do with VBProject.

Yes, VB Extensions are on - well they show up in the VBE-> References screen.

Also, what area in VBE do I put this coding?

Still trying to figure this out as I have a project I will be involved in that may use this type of coding/macro.

Please help

If I need to put more info in, let me know.

When you open the VBEditor and select References from the Tools menu a dialog box should appear. Is the
Microsoft Visual Basic for Applications Extensibility library checked?
If not, check the box and press OK.

That's Done!

If you are writting code for distribution, you'll need to include code that opens the user's VBIDE library.

What are you doing with this?

If you are creating and destroying UserForms, people can give you a lot of reasons why that is usualy a bad idea. (My favorite argument against that practice is that it makes your file grow larger with each use.)

Is your VB routine writting code to a module?

(If you need to keep the VBE window invisible, you must be doing something unusual (i.e. interesting).)