Selling an executable
HI GUYS! MISS ME?
(BTW...........WHO is Lori and where are Paul and Phil?)
Here's the deal:
I worked for <large oil co. that start with an "e"> a couple of years ago and designed a database for some engineers. Now THEIR boss has retired and wants me to do the same (almost identical) thing for him so that he can use it as a consultant to the oil industry.
Now that I work for a software company, I realize that I should create the software for the guy in VB using an Access backend and sell it to him rather than doing work for him on an hourly basis and HE own the code. But, the problem is, until now, I didn't have to worry about deployment of <whatever> because I worked in small companies and could install whatever I needed to manually.
SO.........How do I go about deploying an executable with all relevant dll's? Also, can I create Crystal Reports and somehow include them in the executable? Does CR have to be installed on the recipient's machine? A viewer?
The database that I originally created (or should I say "WE" created?) was in Access and I've learned a LOT since then. I left them <large oil co. that starts with an "e"> an .mdb file that could be editted. I don't wanna do it that way now. I want to create a VB6 executable that has an Access backend but I want to be able to lock down everything I can so that if they need any additional reports or enhancements, they will have to come to ME.
Please give me any feedback you can but PLEASE don't be negative. I've had enough of THAT for a lifetime.
Thanks, Guys!
Love & Kisses,
L
[1706 byte] By [
Laurel] at [2007-11-11 8:26:28]

# 1 Re: Selling an executable
Lori is the dev-archive Editor-In-Chief and forum Administrator.
Regarding the deployment of your app, it might help to find out what sort of deployment software and processes the company may already have in place. This way you could develop a package they could deploy through an existing system. If you just need a conventional installer then I would recommend taking a look at Inno Setup (http://www.jrsoftware.org/isinfo.php). I can't recommend the Visual Basic Package and Deployment Wizard since it is now outdated with respect to the latest versions of Windows and lacks custom configurability.
Crystal Reports implements runtime files that must be distributed with your application. You could check the Microsoft Knowledge Base or with Business Objects (http://www.businessobjects.com/) in order to determine what is required.
It's rather difficult to lock down an Access database, especially when there is an application (Microsoft Access) that is capable of opening it, not to mention features that enable end user creatable functionality.
However, you already control the functionality provided by your Visual Basic app. That is, unless a requirement of the software contract is that you provide the source code. You may want to consider using another database product for your data store, such as VistaDB (http://www.vistadb.net/products.asp).
# 2 Re: Selling an executable
Hi Laurel
A good deployment package will also include the Crystal files required (e.g. InstallShield) and the user will not need to install anything else. We do exactly what you are referring to (VB, crystal, Access [and SQLServer where required] and it works well).
With Access db you can set up a password that prevents users opening it (*) but which you use in your app when you open it.
(*) Security works for almost all users, but can be cracked.
Hope this helps
Greg
gupex at 2007-11-11 17:26:32 >

# 5 Re: Selling an executable
ciao L, always nice to hear from you
what I do not understand is: do you "at this time" currently work full time for a software company? if yes, does this guy asking you to do a job as an employe of that company or as a private? Another question: will this guy use this application claiming that he wrote it? Yet another question: you wrote and sold this application as a consultant (if I understood correctly) so be sure that you are not selling it twice, the first customer can sue you! It seems confusing to me (but I am NOT being negative!)
Regarding Access: are you sure that it is the best solution? A mdb database can work fine as for small applications or for learning SQL, but it has a lot of very nasty limitations (and it is almost impossible to protect).
Marco
mstraf at 2007-11-11 17:29:30 >
