• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 550
  • Last Modified:

Emailing a Excel Compiled EXE using : http://orlando.mvps.org/XLtoEXEMore.asp


EE Professionals,

I used a tool from : http://orlando.mvps.org/XLtoEXEMore.asp  to convert a XLSM file to an EXE and on my computer it worked great.  Then I emailed it to my other computer to test it out.  When it arrived, it arrived as an EXE. When I saved it, it saved as an EXE but showed as a Excel file.  I opened it and then was able to save it as a XLSM file that is then again completely modifiable.  This defeats the purpose of compiling the code.  Can someone who is familiar with compiling XLS or XLSM files to EXE perhaps help me with the default selections?  I'm simply trying to distribute a XLSM file, in an EXE format that cannot be modified without the original XLSM file.

Thank you,

B.
0
Bright01
Asked:
Bright01
  • 5
  • 5
1 Solution
 
bright12Commented:
Why don't you password protect the file?

0
 
Bright01Author Commented:
Could it be that simple?  So if I protect the workbook and then compile it, although someone can save it as a xlsm file, you still can't access the developer window?

B.
0
 
bright12Commented:
I think it is that simple. Just give it a try to see if it works.

And maybe you don't have to compile it.
0
Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

 
Bright01Author Commented:
Just tried it and can still crack it easily.  I think I'm going to have to purchase LockXLS.

B.
0
 
bright12Commented:
What do you mean with easily to crack? Maybe it works in combination with protecting the sheet first, and then protect the workbook.
0
 
Bright01Author Commented:
So I protect the sheet, the project and the workbook.  I then compiled it.  Then I sent it via email to my other system (test).  I opened the XLS and then I have access to the Dev. Tab; and I have full access to access, via the password, the code.

I"m trying to compile to protect the sheet.

B.
0
 
bright12Commented:
Why should you compile it? If the workbook is already protected?
0
 
Bright01Author Commented:
My understanding was that there were easy ways to get around Excel security.  Compiling provided better protection.  Is that incorrect?  

B.
0
 
bright12Commented:
It is true that the excel security is not that good.
Maybe compiling will help as long as the compiler don't remove the protection that has been set in excel.
0
 
Bright01Author Commented:
B12,

I finally gave up and went with LockXLS tooling.  Works like a champ.  Compiles easly and is locked down solid.

Thanks,

B.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 5
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now