Two Questions...

R

R-Enemy

Two questions about things working just fine on my
machine and not another:

1. Setting up a command bar:
I used "Set MyBar = CommandBars.ActiveMenuBar" and this
worked just fine. But, I take it to a different machine
and I have to Dim MyBar As CommandBar to get it to work.
Why is this? I have to Dim all of the CommandBar Buttons
too, rather than just using Set like on my machine. So,
if I Dim everything it works but that's alot of extra
lines of code.

2. Creating a MsgBox:
I have message that I want split into multiple lines so
on my machine I used Chr(13) which is the carrage return,
works just fine. But, the other machine doesn't recognize
Chr and I get an error. How can I get around this or what
file (library) do I need to install on the other machine
to get this to work?
example: MsgBox("Line #1" & Chr(13) & "Line #2")

Thanks.
 
E

Edwin Tam

(1)
Your other computer had the option "Require Variable Declaration" activated in VB Editor.

In VB Editor, from the Tools menu, choose Options, the Editor tab.

(2)
Try using Chr(10) instead.
 
R

Rob van Gelder

1. I have examples of CommandBars on my website.
2. Suspect broken references - I have some code for broken references on my
website.
 
C

Chris Lacey

Re your first question :-

Is the "Option Explicit" statement present in the General
Declarations section of the code module in which you have
placed your code? That would force you to "Dim" variables
etc. before initialisation/use.
=========================================================
Re your second question:-

Use the predefined VB constant "vbCrLf", instead of
Chr(13). That should work anywhere.

Regards
Chris
 
M

Mark Worthington

Rob van Gelder said:
1. I have examples of CommandBars on my website.
Click to expand...


Rob,

I have tried your code ref "Buttons for VBEIDE", but could only get it
to work by adding a reference to "Microsoft Visual Basic for
Applications Extensibility". Is this actually required? If so, the
information line is missing from your site.

Secondly, is there any way to stop the screen changing to the
worksheet (ie, stop the code exiting the VBEIDE)?

Cheers,

Mark
 
Top