Re: dll or exe file creating
The only version of Offic that did any kind of compiling was Office XP Developer version. It was developer extensions and other stuff.
If you want to protect your vba code then you could provide a strong password and protect your project from viewing in the
Tools > Project Properties... and the check Lock this project from viewing and supply your password. Note: Yes there are some VBA password
crackers out there but if you create a strong password they usually can not crack it. I have not heard of too much positive feedback from
anyone using these.
To eliminate the "ThisOutlookSession contains macros message you can create a Digital Signature (private) and sign your code with it. Then
trust your signature and it should go away.
I have a CodeBank entry on creating a Digital Signature. :)
Re: dll or exe file creating
hi..
Thanks for the answer.
In case i choose th password way, is it prevents from my users to create there own add-ins? And i don't actualy see how can i distribute the project this way? How will i do updates....
I don't want to distribute Microsoft Office that contains my code, i want to distribute my code only..
Is there some other way??
10x,
anastacia
Re: dll or exe file creating
Office is not redistributable but you code is. If you had VB6 you could creaate an Add-In dll wich would solve the problem.
Re: dll or exe file creating
If i'll install the VB6 , should i change my VBA code that runs in Outlook vb6 editor or i can copy it to VB6 ??
Is the relation to outlook application and MAPI .. differes from VB6(created dll)?
Should i write the code from the beginning ? :'(
10x
Re: dll or exe file creating
The vb6 addin code is almost the same but you should just need to make some minor changes at a minimum.
There wont be the events in the Addin exactly the same but you just need to declare a WithEvents object of the type you need and
then your bak in business.
Outlook Application and MAPI are the same in VBA and VB6.