Compiling a paradox9 application

[lemonjuice]

We used paradox9's application framework to create an application. We have the full developers addition. Does anyone have guidelines for us to compile this application to run on a machine where paradox9 has not been installed, but only the BDE? Do we have to supply the paradox9 runtime with the application to the client?

 

[footpad]

lemonjuice,

Yes, you'll need to proivde your client with Paradox 9 Runtime.

You can't compile Paradox applications into .EXE's, like you can with a traditional programming language. Instead, you bundle things together, provide BDE and Runtime, and deliver the final package to your client.

Paradox 9 includes the PDE, which you may find helpful. A lot of people didn't like it because it didn't provide a lot of options, but there were also a lot of people that liked it.

If you end up in the former camp, you may want to look at InstallShield, which can be used to create an installation file.

Hope this helps...

-- Lance

 

[jlockley]

Lance: I have to put together a short database for the board members of a local organization. None has Paradox, so could you be a bit more explicit? Where do I find Install Shield (I have Paradox 8 and Paradox 10). I believe I can download runtime from the Corel web site. 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?

Thank you.

 

[footpad]

jlockley,

>> 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...

-- Lance