Thank you both for your speedy replies!

Bob: I did as you said, selected "Break Class Module", and there is no
change--it still breaks on the same line of code (i.e. on
frmKitForms.Show).

The strange thing is I can open the VBIDE, go to the procedure and push
F5 (or step through with F8) and everything works fine. The problem
occurs specifically when I run the macro from the cmd btn on my
worksheet.

Any more thoughts are greatly appreciated!

Regards,

Tim

Bob Phillips wrote:
You can force it to break on the actual error.

In the VBIDE, goto ToolsOptions, select the General tab from the dialog,
and set the 'Break in Class Module' button in the 'Error Trapping' frame.

--

HTH

Bob Phillips

(replace xxxx in the email address with gmail if mailing direct)

"michael.beckinsale" wrote in message
ups.com...

Tim,

Unhelpfully if there is a coding error contained in a form the debugger
will the highlight frm.show code line.

I usually find that its the 'initialize' event that causes this but
that wont neceesarily be the case.

Suggest you can try 'commenting out' sections of code to isolate what
causing the problem or if possible paste the code into a normal module
and run from there.

Regards

Mike beckinsale