Conclusion
As developers of applications, it's all too easy for us to assume our user interfaces are so intuitive and easy to use there's no need to provide a help file. In reality, we can only achieve that level of simplicity with the most trivial features. Including a well-written help file with our application can provide the explanations our users require to effectively use the features we provide. The increase in confidence that brings will often lead to an improved perception of the entire application.While developing Excel applications, we usually don't include any security restrictions, because they tend to get in the way of our work. We must, however, consider the security implications of everything we do, both in terms of whether our application could be misused and whether our application can be broken into.Excel is not a secure environment; a malicious hacker can access any worksheet or VBProject in any workbook using tools readily available on the Internet. If we want to protect our code from the determined hacker (rather than accidental change), we must move it outside of Excel VBA, usually into VB6 DLLs.When distributing our applications to end users, we usually need to provide an installation routine to ensure all our files are copied to the correct folders and write any registry entries that may be required. This is most often done using a separate setup.xls workbook, which can use the Excel object model to copy the files, install add-ins and so on. For a professional look, however, we should be creating proper installation routines using a commercial installer package such as WISE or InstallShield that can also be used to uninstall our applications. |
لطفا منتظر باشید ...
