Creating an .exe

[Stoven]

Is it possible to creat an .exe file in Excel 2007 or 2010?

 

[xenou]

I'm not sure when you say "the other link" whether you meant the link in post #2 or post #5. The Link in Post #2 seems to be broken. The link in Post #5 should work. Here it is again (the 5th and 6th posts in this thread are the ones I wanted to provide):
[link deleted - broken see post #13 below for more info]
ξ

 

[Stoven]

The link in post #11 tells me I do not have permission to access it.

 

[xenou]

Okay. I have no idea what is wrong - I've never had trouble posting links before here. Just search for posts by Digiwise (forum member who made the post) and/or Doneex (keyword - one of the Excel compilers.).

This is Digiwise's Post:

I haven't tried any of these, but I've researched a list that might be helpful:

Donex XCell Compiler: http://www.xcellcompiler.com/
Spreadsheet Sentry: http://www.spreadsheetsentry.com/
Tip for VBA hardware locking: http://www.yogeshguptaonline.com/200...-workbook.html
Excel Translator: http://www.exceltranslator.com/EThome.htm
DatasafeXL: http://www.datasafexl.com/protect_mi...xcel_files.htm
Secure Calc: http://www.praetorians.eu/
LockXLS: http://www.lockxls.com/start.asp?id=dnld
Converter XL to Exe: http://cpap.com.br/orlando/XLtoExeMore.asp

I too would be interested on feedback on any of these.

Clancy

This is WhiteHatXL's reply:

Ta-Da….
This is the parade of Excel workbook protection tools!
I have focused on the base features of the products which affect the security and misbehavior of protected solutions.

DataSafeXL:
PROS: A newbie in Excel cannot reach the content of the protected workbook.
CONS: The product is programmed in vba. The tool relies on standard MS Excel protection methods like workbook/worksheet protection and vba project password plus the vba code obfuscating. You do not need to be C programmer to pass over such protection.
“For maximum VBA security, use the Microsoft Excel 2007-2010 format (".xlsm") and add a VBA password to your file which contains random alphanumeric characters and is at least 15 characters long.”
This advice from their help file just kills me!
Looks like the guy who wrote this product has been learning vba programming by the way.
SUMMARY: Junk. The product is on a student project level.

Spreadsheet Sentry:
PROS: The tool is programmed in C++, uses strong encryption to protect formulas in cells. In protected solution formulas are encrypted, stored in cells and not readable.
CONS: Takes WAY too much time to encode a workbook even for middle size model.
Protected solutions work veeeery sloooow. Calculation time is wasted for encryption/decryption every formula in calculation chain.
The tool doesn’t protect VBA code.
SUMMARY: Protection works. The tool appropriates for small workbooks without VBA macros.

LockXLS:
This is the most controversial product in the review. After the first glance I wanted to give “the perfect” mark, but see what I have finally found ….
PROS: The tool is programmed in C++. In protected solution everything works like in original workbook. Average user cannot see formulas in cells and vba code in protected workbook. Protects xla files. Lots of features.
CONS: The product uses unmodified, original workbooks in protected solutions and relies on hackers’ methods to take customer away from seeing the content of the workbook (Hooks Excel windows and blocks Excel’s COM objects methods calls). The tool is trying to stub all Excel’s security breaches, which is impossible with an unmodified, original workbook.
When a protected solution has been started on an end customer computer, the spreadsheet becomes as unprotected as newborn baby.
5 lines of C code extract the original workbook from the protected solution, doesn’t matter whether it’s xls or exe file.
To prove the vulnerability of LockXLS solutions, just e-mail a protected solution to WhiteHatXL at yahoo dot com , the original workbook will be returned.
SUMMARY: Fake. This product is not for a workbook protection.

Secure Calc (former ExcelShield):
These guys have ignored my requests for a trial version, so I have evaluated the product by the simple example from their site—It may work different for complex spreadsheets.
PROS: The tool uses strong encryption for formulas, removes formulas from cells, has calculation engine to evaluate protected formulas.
CONS: Engine is written in .NET environment in pure managed code, which is not good for a protection tool. Source code may be reached by Reflector and reverse engineered. No VBA Protection.
The calc engine is not included into protected solution and should be preinstalled on customer computer separately. Each time, after typing new data into cell, the customer has to click the ‘Calculate’ button, which is available through the main Excel menu. This is very annoying.
SUMMARY: Protection works. It looks good enough, if you do not need to protect vba code.

xCell Compiler:
PROS: The tool is programmed in C++, compiles formulas into binary code and removes them from cells, protects vba code. Has calculation engine to evaluate protected formulas. Has a lot of features.
CONS: The tool has limitations declared on their web site. A protected solution doesn’t support adding/removing columns/rows/sheets. Sorting for ranges with formulas doesn’t work.
SUMMARY: Protection works. Good, if you do not use features mentioned in limitations.

Excel Translator:
I was unable to get the neither trial version nor example of protected workbook. Very “strong” protection!


Converter XL to Exe:
PROS: Free, Free, Free!!!
CONS: This tool is not for a workbook protection.
SUMMARY: Toy.

I hope it will help someone….

 

[Stoven]

thanks for clearing that up, it gives me lots to look into.

 

[T. Valko]

That's wierd. My BB Code is:
excel compilers

This is supposed to be post #5 in this thread:
http://www.mrexcel.com/forum/showthread.php?t=232464

I get the same message with that link!

 

[xenou]

No problem. I've never used these products but in general I'd watch for whether or not they support the newest (xlsx) file formats or not. I'm not really sure what happens on the user's end - whether changes can be saved or the files are "read-only". Someday I'll have to try it out.

@T. Valko:

I get the same message with that link!

I hear ya. This is most strange. I've sent a message to the admins - not sure what's up as I've never had this behavior before. Maybe it's just one of those days.

 

[martindwilson]

fwiw i also get

martindwilson, you do not have permission to access this page. This could be due to one of several reasons:

Your user account may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

in links posts#2 and#5

 

[Bazilc]

I see this is an old post, however, if you are still looking for a way to create .exe from Excel then checkout xls padlock. They have a free version for testing your own docs and a paid version when you want to distribute your files. The link is Download XLS Padlock.

Hope this helps.