>> None has Paradox, so could you be a bit more explicit?
Sure; you'll need Runtime, so your users can actually run the forms, reports, and so on. Since you have Paradox 10, you have a license to download and redistribute Paradox Runtime applications.
>> Where do I find InstallShield.
InstallShield is a commericial Windows installation creator.; information is available from http://www.installshield.com/
and you should be able to purchase a copy from either the company or any major online software retailer (e.g. CompUSA, etc.).
Alternatively, there's a free package that does the same thing called Inno Setup (http://www.jrsoftware.org/isinfo.php
). I mention it because the price is right and there's a new FAQ on dbcommunity that showqs how to use it to create setups for Paradox Runtime applications. See http://thedbcommunity.com/code/innoinst.htm
for details. In addition, they have a forum where you can discuss any problems you find with the article.
>> If I bundle the products in a zip file,
>> do I instruct the recipients to place all
>> items (.db, .fsl, bde ) in the same folder?
Actually, the setup program will bundle the files for you; you don't need to compress them yourself. Also, it will handle installing the files to wherever the user wants them.
Mind you, you need to make certain that your application can be run from wherever it's installed to. The best way to do that is to design the forms, reports, scripts, and so on to use aliases to point to the files, even if you're using the :WORK: alias.
In my applications, I used project aliases that are defined when the application starts. While this adds a bit of work for me as a developer (I have to run a definition script each time I start Paradox to work on the project), it actually streamlines things in the long run.
Now, this is a huge issue, one I could probably go on about for hours. Why not start with Inno and the FAQ I mentioned and see what sort of questions you run into. We'll handle those as they come up.
Hope this helps...