¨ FrontPage ¨ Outlook ¨
¨ Miscellaneous ¨
It's unfortunate that I must provide this information, but want to protect buyers from selfish or unethical programmers. Here's a few guidelines on purchasing programming for a resellable application, for personal or inter-company use, and how to choose the right application for your project.
If you are creating a product that you plan to sell, don't bother having it developed in the Microsoft Office application, or do so knowing that your ultimate plan will be to have it developed using Visual Basic (not VBA). COM add-ins are one way to make an application more secure. An add-in works with the application to provide additional features. However, if you create, for instance, a entire Excel workbook that provides cool reports for stock market data or something like that, then have it developed in VB. Quite simply, you cannot secure a Microsoft Office application or keep anyone from copying it from machine to machine.
If you choose to have a Visual Basic stand-alone application developed, then what you should ensure you are buying is the application and the source code. Do not make final payment until you have received the source code, or you have the working application and have been promised the source code upon final payment.
If you have found a developer that is agreeable to all the above, you may be able to pay a reduced fee or even no fee by agreeing to share the profits with the developer.
I have just read a post where someone is asking how they can restrict access to their VBA code so their client cannot access it. I refused to answer and told them why. If you are buying VBA code—automation, macros, call it what you will—then you should certainly have access to it. Your programmer may wish to protect the code until you've paid the bill, but you should certainly have access to your code once the job is finalized. Why? Well, what happens if you hire someone next year to enhance the features in the project? Should you have to make them rewrite all that code? NO! You have paid for that code. Not only should you have access to it, but it should be heavily commented so that any programmer can understand what it's doing.
Here are some bad reasons for choosing an application when you are paying to have it developed for you:
Too many people program Excel applications instead of moving to Access when they should. And they go to an Excel developer for more work. If the Excel developer doesn't also develop Access applications, he'd be shooting himself in the foot by telling you it ought to be in Access.
Can't figure out what to do with your application? Contact My Experts Online for a free consultation.
OfficeArtilces.com debuted on May 26, 2005.
MrExcel.com provides examples of Formulas, Functions and Visual Basic procedures for illustration only, without warranty either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose. The Formulas, Functions and Visual Basic procedures on this web site are provided "as is" and we do not guarantee that they can be used in all situations.
Access®, Excel®, FrontPage®, Outlook®, PowerPoint®, Word® are registered trademarks of the Microsoft Corporation.
MrExcel® TM is a registered trademark of Tickling Keys, Inc.
All contents © 1998-2014 by MrExcel Consulting | All rights reserved