Distribute Project 2003 Macro

[Dory]

I have a client who wants me to write VBA Macros for Project 2003 and then
sell them to other companies. Is there a way to deploy VBA Macros? I come
from a VB background so I am a little lost when it comes to distribution of a
Macro other than simply coping the code or importing a vba module file
manually.

Any ideas?

 

[Jan De Messemaeker]

Hi,

Within one company I did it by creating a MSP file with an auto open module
that transferered the objects to the user's global.mpt (modules, toolbars,
custom fields...)
HTH

 

[Dory]

thanks for the reponse, but I am a little confused. How does a windows
installer file actually open up the global.mpt, add module, the save it again.

Also, what if the user is not an adminstrator?

thanks

-dory

 

[Jan De Messemaeker]

Hi,

Sorry but my post clearly said an MSP file, that's a Microsoft Project file.
I wouldn't know the difference between a windows installer file and a pink
elephant, I'm strictly a one trick pony.

When you open it, the global opens automatically.
HTH

 

[Dory]

Sorry about the .msp confusion, but I have Project 2003 and the file
extension is .mpp not .msp

 

[John]

thanks for the reponse, but I am a little confused. How does a windows
installer file actually open up the global.mpt, add module, the save it again.

Also, what if the user is not an adminstrator?

thanks

-dory

dory,
While at my company I did the same thing as Jan, but that approach isn't
the best if you are trying to "sell" macros to other companies. Of
course you can always put the module with your code into a blank Project
file and then provide ("sell") that to anyone who has Project. That is
basically what I do now, but then I really only do it on a very casual
basis.

Just curious, why would a client want you to write code and sell it to
someone else? It doesn't make a whole lotta sense. Normally you would
perform a service (e.g. develop a macro) for a client and they would pay
you. Other potential "customers" would be separate clients.

You mentioned something about a Windows installer. With VBA macros, a
Windows installer doesn't enter the picture. The closest thing that
approaches that is creating stand along VB applications with something
like VB6 or VB.net. You might want to find out more about those
development tools.

John
Project MVP

 

[John]

Sorry about the .msp confusion, but I have Project 2003 and the file
extension is .mpp not .msp

Dory,
Let me clarify the apparent misunderstanding. MSP stands for Microsoft
Project - it is an abbreviation, not an extension. When expressed in a
DOS format an MSP file has an .mpp extension.

Just to clarify one other thing. Jan actually does know the difference
between a widows installer and a pink elephant. A windows installer is a
guy who comes to your house and replaces an old window with a new one.
On the other hand a pink elephant is a really potent mixed drink (grin).

John

 

[Rod Gill]

Yep and Jan forgot all about the first one after too many of the pink
thingies!