how to set macros toolbar unviewable to users?

J

Joy

we wrote some macros and built a toolbar

but we do not want user to view our source VB code of the macros. can we set
it not viewable?

but how to do that??
thanks!!
 
J

John

"Stephen Sanderlin" <stephen NS-DOT sanderlin A-NS-T msprojectexperts
DOT-NS com said:
The other option is to use VSTO instead of VBA.

--

Stephen Sanderlin

Principal Consultant

MSProjectExperts
Click to expand...

Stephen,
OK, for the uninitiated amongst us, what is VSTO?

John
Project MVP
 
R

Rod Gill

Hi John,

It's Visual Studio for Office. Use it to create Add-ins for Project. You
combine the power of VB with Project. I've done one now and apart from the
learning curve, it's good!

--

Rod Gill
Microsoft MVP for Project

Author of the only book on Project VBA, see:
http://www.projectvbabook.com
 
J

John

Rod Gill said:
Hi John,

It's Visual Studio for Office. Use it to create Add-ins for Project. You
combine the power of VB with Project. I've done one now and apart from the
learning curve, it's good!

--

Rod Gill
Microsoft MVP for Project

Author of the only book on Project VBA, see:
http://www.projectvbabook.com
Click to expand...

Rod,
Thanks for the info. When "non-standard" acronyms are used in responses
I feel it's important to spell out what they stand for. But maybe that's
just one of my quirks.

John
 
S

Stephen Sanderlin

John,



While I agree "non-standard" acronyms should be spelled out, I disagree
that VSTO is a "non-standard" acronym.



VSTO is the official Microsoft abbreviation for the Visual Studio Tools
for Office (regardless of version) and is used extensively in MSDN and
elsewhere. In fact, it appears ten times on the Visual Studio Tools for
Office Developer Portal
(http://msdn.microsoft.com/en-us/office/aa905533.aspx). Therefore, I
think that it's fair to consider VSTO a "standard" acronym just like VS,
NetFX, MOSS, SSRS, SSAS, ODBC, IIS, OCS, and WSS are all considered
"standard" acronyms.



Steve

--

Stephen Sanderlin

Principal Consultant

MSProjectExperts



For Project Server Consulting: http://www.msprojectexperts.com

For Project Server Training: http://www.projectservertraining.com



Read my blog at: http://www.projectserverhelp.com/

Join the community at: http://forums.epmfaq.com
 
R

Rod Gill

C# is a great language, but when interfacing to an Office program, the named parameters and optional parameter alone makes for much easier to read code and hence cheaper to maintain code. Plus the ability to copy paste VBA code and have it work with only minor editing means VB is more productive, especially for learner VSTO users.

Once you are skilled and experienced it is of course personal choice.

--

Rod Gill
Microsoft MVP for Project

Author of the only book on Project VBA, see:
http://www.projectvbabook.com



"Stephen Sanderlin" <stephen NS-DOT sanderlin A-NS-T msprojectexperts DOT-NS com> wrote in message Or C#, depending on your preference :eek:)



But, it's much more powerful than VBA, and if you already know a .NET language, the learning curve isn't very large.

--

Stephen Sanderlin

Principal Consultant

MSProjectExperts



For Project Server Consulting: http://www.msprojectexperts.com

For Project Server Training: http://www.projectservertraining.com



Read my blog at: http://www.projectserverhelp.com/

Join the community at: http://forums.epmfaq.com
 
S

Stephen Sanderlin

I can agree with that :eek:)



--

Stephen Sanderlin

Principal Consultant

MSProjectExperts



For Project Server Consulting: http://www.msprojectexperts.com

For Project Server Training: http://www.projectservertraining.com



Read my blog at: http://www.projectserverhelp.com/

Join the community at: http://forums.epmfaq.com





"Rod Gill" <rodATproject-systemsDOTcoDOTnz> wrote in message
<
C# is a great language, but when interfacing to an Office program, the
named parameters and optional parameter alone makes for much easier to
read code and hence cheaper to maintain code. Plus the ability to copy
paste VBA code and have it work with only minor editing means VB is more
productive, especially for learner VSTO users.



Once you are skilled and experienced it is of course personal choice.


--

Rod Gill
Microsoft MVP for Project



Author of the only book on Project VBA, see:
http://www.projectvbabook.com






"Stephen Sanderlin" <stephen NS-DOT sanderlin A-NS-T msprojectexperts
DOT-NS com> wrote in message

Or C#, depending on your preference :eek:)



But, its much more powerful than VBA, and if you already know a .NET
language, the learning curve isnt very large.

--

Stephen Sanderlin

Principal Consultant

MSProjectExperts



For Project Server Consulting: http://www.msprojectexperts.com

For Project Server Training: http://www.projectservertraining.com



Read my blog at: http://www.projectserverhelp.com/

Join the community at: http://forums.epmfaq.com
 
J

John

"Stephen Sanderlin" <stephen NS-DOT sanderlin A-NS-T msprojectexperts
DOT-NS com said:
John,



While I agree "non-standard" acronyms should be spelled out, I disagree
that VSTO is a "non-standard" acronym.



VSTO is the official Microsoft abbreviation for the Visual Studio Tools
for Office (regardless of version) and is used extensively in MSDN and
elsewhere. In fact, it appears ten times on the Visual Studio Tools for
Office Developer Portal
(http://msdn.microsoft.com/en-us/office/aa905533.aspx). Therefore, I
think that it's fair to consider VSTO a "standard" acronym just like VS,
NetFX, MOSS, SSRS, SSAS, ODBC, IIS, OCS, and WSS are all considered
"standard" acronyms.



Steve

--

Stephen Sanderlin

Principal Consultant

MSProjectExperts
Click to expand...

Steve,
When I say "non-standard" I'm thinking of interpretation or
understanding by an average user, not someone who is versed in Visual
Studio or other advanced development tools. Perhaps I'm wrong, but the
context of the original post lead me to believe the poster was an
"average" user who had written some basic VBA code. Therefore I made the
assumption that they might not know what VSTO stands for, so I asked the
question - at the risk of also displaying my own ignorance.

John
Project MVP
 
S

Stephen Sanderlin

John,



Fair enough. I didn't understand what you meant by "non-standard", but
now that you've explained it, I see your point and find that I agree
with you.



It's very easy for us to get caught up in jargon, especially when those
of us who respond to questions post in response to each other. It's easy
to forget that this isn't email (especially when you have your
newsgroups showing in Outlook!). I'll make it a point to spell out
acronyms in the future so that everyone feels like they are part of the
conversation.



Thanks the feedback!



Regards,

Steve


--

Stephen Sanderlin

Principal Consultant

MSProjectExperts



For Project Server Consulting: http://www.msprojectexperts.com

For Project Server Training: http://www.projectservertraining.com



Read my blog at: http://www.projectserverhelp.com/

Join the community at: http://forums.epmfaq.com
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Incorporating the User Profile location into a document template path 1
Need Help with Macro Security 1
MS365 WORD: How to Create Macro Button to CLEAR ALL fields in fill-in form 1
Can we use outlook calendar as an universal place post work schedules for all the users? 0
Tracked changes by multiple people modified to one 0
Clearing Fields in a Word Form 5
Office 365 documents default header 1
VBA word change keys 0

Top