Paradox 7 Runtime to Paradox 10 Runtime? Should I?

[LWB]

I have an application that runs in Paradox 7 Runtime. I own (but haven't used) Paradox 8 Runtime (as well as Paradox 8). I never bought Paradox 9 (the developer edition was pretty expensive) or 10. I never made the conversion to Paradox 8 because of printing problems with Paradox 8.

I'm debating upgrading to Paradox 10 and moving the distributed version into Paradox 10 Runtime. So my question is should I? Or am I better off sticking with Paradox 7 (or trying to find a version of Paradox 9).

I've heard that there is no install package included with Paradox 10 Runtime. Is it possible to use the InstallShield that came with Paradox 7? If not, how do you produce an application distribution disk? I believe a different installation package (something besides Install Shield) came with Paradox 8 Runtime. Does it work? I've never attempted to use it. It took me so long to get InstallShield to work right I'm reluctant to change

If I take the leap to Paradox 10, how big is the download for Paradox 10 Runtime? Is my dial-up ISP up to the task, or do I need to recruite a friend with a fast connection?

Lynn

 

[footpad]

LWB,

While Corel hasn't made what one might call major changes to each new version of Paradox, there have been some pretty significant changes since version 7, enough that it might make sense to upgrade. For example:

-- Since Paradox is no longer sold separately, you'd only need to upgrade to the Professional Edition of WPO 2002, whicyh includes a license for Runtime. This means you'll pay about $250 for something that would have run about $500-$600 in older versions.

-- In Paradox 8, Corel added some internet functionality that's been slowly improving in the interim. While the v8 stuff was slightly touchy, the more recent versions are far better. Indeed,

http://thedbcommity.com

is implemented with Corel's Web Server running against Paradox tables (or so I've heard).

-- There have been rumors that Corel ported Paradox to VC (from BCC) in version 9. I can't say whether these are true or not, however, I can tell you that many of the memory leaks found in older versions seem to have gone away. It seems far more stable now.

-- During Paradox 10 development, I know that a lot of attention was paid to the long outstanding report problems that first surfaced with the 32-bit port. You still have to deal with things like the stylesheet issue, but a lot of the "squirrlies" seems to have gone away.

-- Other new enchancements include tooltip properties, string lists (which can drastically reduce the code needed to build menus and keyboard shortcuts), direct writeToFile method added for reports, ability to detect corrupt tables from within ObjectPAL, enhanced experts, and so on.

Like I said, there's nothing that really jumps out at you until you look at the whole picture.

As far as using the InstallShield that was provided with Paradox 7, I haven't personally tried that (I prefer Wise myself). However, I do know there's an InstallShield FAQ at

http://www.thedbcommunity.com/faq/12.htm

that looks fairly complete.

The Paradox 10 Runtime (SP2) download is ~40MB, so I'd definitely butter up your friend with the highspeed connection.

Hope this helps...

-- Lance

 

[LWB]

Lance,

Thanks for the advice. What is Wise?

I guess I see the main advantage for upgrading is not having to explain the Application Compatibility stuff to Windows XP and Windows 2000 to users (who often understand very little about computers).

And I see the main disadvantage for upgrading is trying to figure out the distribution software. (If the old InstallShield Express from Paradox 7 works that should make things a little easier. I remember having real struggles with InstallShield before I finally got it to work correctly. And I unfortunately no longer remember all the details.)

If InstallShield Express won't do it, what should I try? I have Runtime 8 - which includes some other distribution software, but I know nothing about it.

Lynn

 

[ojn]

Hello!

Several Paradox users have switched to using Inno Setup. See:

http://www.jrsoftware.org/isinfo.php

.

HTH,
O.J.

 

[Langley]

OJN,

I looked at the Inno link and I'm not sure how you would deliver Paradox Runtime with it. I've always used the PDE, so I am ignorant as to how to deliver the Runtime Files using 3rd party software. Can you offer any insight? Thanks!

Mac

"There are only 10 kinds of people in this world... those who understand binary and those who don't"

langley_mckelvy@cd4.co.harris.tx.us

 

[ojn]

Hi Mac!

OK, I haven't used Inno myself, though, IIRC, I was the first to suggest using it with Pdx (about 1 to 1.5 years ago). There have been several threads with a couple of developers having created Inno scripts to install Pdx and the BDE. One of them is in the process of writing a short article on how to do this.

If you do a Google newsgroup search or search the Pdx related threads at the cnews.corel.com and pnews.thedbcommunity.com newsgroups, you will find many discussions on using Inno with Pdx, runtime, and the BDE.

BTW, the reason I initially suggested Inno for Pdx was that I saw that dBase, Inc. was recommending (at least at the time) using Inno as the official dBase installer (it actually was including on the dBase CD) as it was designed handled the BDE. (Inno is written in Delphi.)

HTH,
O.J.

 

[footpad]

Lynn,

Wise refers to Wise Installer for Windows, an installation package similar to InstallShield, though a bit different.

The main reason I personally prefer Wise to InstallShield is because it's interface simply makes more sense to me as a programmer--geek--type. I've never been fond of IS's wizard based, hands-off approach. WISE has a wizard, of course, but you can turn it off, read the actual installation script, and modify it as you need to. While there are things about Wise I don't like, I've learned to live with most of its quirks over the past few years.

I've heard good things about Inno, though I've not used it personally. If budget is a concern, I'd definitely take a look at Inno; if I recall correctly, it's slightly cheaper than either Wise or IS.

Also, Mac, as far as installing a Runtime application goes, you basically need to make certain that:

1. Runtime itself is installed properly.
2. Registry entries are properly made (which is made easier through some of Corels available .REG files; scan the folders).
3. Your data and document files need to be installed
4. BDE needs to be installed.
5. Any public aliases need to be saved into the BDE/IDAPI(32).CFG file. (Note: this is why I almost always advocate project aliases as opposed to public ones.)
6. Any shortcuts/icons are installed into the appropriate places.

It seems a lot, but if you look at the IS FAQ I mentioned earlier, you can figure out most of the basics. Also, I recall locating a WISE script for Paradox Runtime applications somewhere on the 'Net a couple of years back. I found it using google, so it shouldn't be that difficult to run up again.

Hope this helps...

-- Lance

 

[LWB]

Thanks everyone for the advice. I have Paradox 10 and Runtime 10 installed on my computer now. The application seems to work okay, but I haven't tested the printing (which worked fine in Paradox 7, but not so great in Paradox 8). It appears that Paradox 7, 8 and 10 can co-exist happily on the same computer.

But all the distribution software is giving me cold feet. I looked at the Inno stuff - it seems like a two step process to do an installation. Plus the documentation mentions things like Delphi scripts. That is out of my league! Besides ObjectPal and a little VBA, my computer languages are limited to old stuff - Fortran, PDP-11 assembler, a bunch of 8 bit assemblers, and a little PL1 and Pascal.

I'm intending to give my old InstallShield Express (that came with Paradox 7) a try. It appears that it might work okay. But if that doesn't work the options get complicated (Inno, Wise, or new Install Shield). Maybe I will chicken out and stick with Paradox 7.

It is steps 2, 5, and 6 in the list that Lance gave that worry me. I guess InstallShield currently does those things, but I have no clue about how. I can see in InstallShield where I provide the info for the other steps. But if InstallShield doesn't do 2, 5, & 6 correctly I will be at a complete loss as to how to fix it.

Lynn

 

[footpad]

Lynn,

Your copy of InstallShield should be able to handle the steps you mentioned, provided you have a 32-bit version, e.g. it came with Paradox 7 for Windows 95/NT.

Looks for commands that:

-- Merge Registry files (#2). You'll want to include the Runtime .REG files in your installation project. You may have to install them to a temporary directory, though I prefer to copy them to a \TOOLS directory below the application directory, just in case something happens to the user's Registry.

-- Copy files (#5). In this case, create a pre-fabricated .CFG file, copy it to your Runtime application's directory, and then start Runime with the -o command line option, which specifies a specific .CFG file for that session. (More information is available at

http://techtricks.com/paradox/cmdline.php3)

-- Create Windows Explorer shortcuts (#6). This should be pretty straightforward, as it's common enough that all installation packages need to do it.

I'm sorry I can't be more specific about InstallShield, but the FAQ I mentioned earlier should offer useful information on locating the specific commands you'll need.

I would recommend creating a simple, practice project to get the hang of the process and test your knowledge. This will give you something you can fiddle with and help gain experience before creating an installation for your application. I've done this frequently using a number of different development tools and have found it very useful.

Hope this helps...

-- Lance

 

[LWB]

Thanks Lance.

I do have the 32 bit version (the InstallShield came with Paradox 7 for Windows 95/NT). It has worked fine through various version of BDE and will all Operating Systems since Windows 95. I run Windows 2000 on my own computers (used to run NT).

The last version of my application in Runtime 7 worked fine under 95, 98, 98SE, NT, ME, XP and 2000. But under XP and 2000 you have to run the Windows compatibility software.

My application isn't that complex. I will try just changing the current InstallShield parameters to the Runtime 10 files and see if that works. It is already installing a current BDE.

I'll let you know what happens.

Lynn