Object required error on CommandButton Click

**rkjudy** · 01-09-2011, 03:39 PM

I don't understand. The form name is correct. Could if be something to do with the properties of the form or the command button? Is there a missing object or something missing in Tools>References? This did work before. I did install the Analysis Toolpack add-in. It slowed down my workbook so much, I uninstalled it. Could this have done something?

**jeffreybrown** · 01-09-2011, 03:43 PM

Is it possible to attach the workbook?

**rkjudy** · 01-09-2011, 04:02 PM

It's probably something simple. Here's the workbook. Thanks, in advance for your help.

**jeffreybrown** · 01-09-2011, 04:29 PM

Hello rkjudy,

Well I sure can't see any reason for this not to work. Hopefullly one of the other members or a Forum moderator will help.

On an aside and still being a rookie, it seems you could just use a regular forms button for a click type procedure versus the active x. Not entirely sure the difference. Guess I need to do some reading.

Also, the slowness could be from the way you have your code. It appears you must have used the macro recorder to get most of your code. There is no need to use all of the Select/Selection.

If you don't mind I will clean some of it up and send you a sample. In the meantime hopefully somebody will come to our rescue.

**rkjudy** · 01-09-2011, 04:32 PM

Thanks for trying. I'm newer to VBA than most. That's why my code is so sloppy. I'll take any advise you can give. BTW, your only seeing a couple of the sheets, the entire workbook has about 12 sheets. Only the ones pertaining to my problem were in the example. Thanks again.

**rkjudy** · 01-09-2011, 04:37 PM

I tried entering the .Show command to a macro and I still get the same error. Any ideas?

**jeffreybrown** · 01-09-2011, 04:42 PM

Hello rkjudy,

Okay, figured out not neccesarily where your problem is; however, I know where the error is coming from.

Go to the VBE and the right click on the frmOrderEntryInfo. Select view code and then temporarily disable all the code.

Now go back to the worksheet and press the CommandButton1. This worked for me so it's telling me you have to clean up, or actually finish whatever code you have behind the frm.

Here is what I found:

Goto Tools>Options... and select Break On All Errors on the General tab.

Now if there is a problem in the initialize event the debugger should go to the line of code causing the problem.

Or create a break point (F9) on a line of code in the initialize event and then step through the code with F8.