Before upgrading 1

[jlockley]

Since I just rebuilt one of my computers I threw in WPOffice 2002 for cheap thrills. I did this the last time I put in a new board, but it caused so much grief, that I simply trashed the thing. (I seem to rember that database engines could not be found).

Obviously everything is going too well now, so I am very tempted to try to upgrade from 8 to 10 again. Before I do, however, can anyone suggest precautions, warnings, etc which will spare grief? (aside from total deletion of the previous program).

 

[footpad]

jlockley,

1. Do a backup. Include the BDE.CFG file, the databases, and even the appropriate Registry branches.

2. Make sure you have plenty of time.

3. Try to download the appropriate patches/service packs before you install and have them ready to go. Install the service packs before you install your database application.

4. Always reboot before--and after--installing the program or any service packs.

5. Always resave all forms, reports, and libraries before running your applications in a new version. (See

http://techtricks.com/paradox/interpret.php3

for details.)

Those are the ideas that occur to me off the top of my head. I'm sure there are others.

-- Lance

 

[jlockley]

I've done it all, and Paradox runs like a clock, but the database (now paradox) for word can't be installed in corel central. That's not a problem for here, though. ("looping&quot
Thanks. (I have now done full manual uninstall of Office 8 and 2002 at least three times. Full reboots. removed borel and corel keys from registry. Same outcome. Corel suggests reinstalling in safe mode from files moved to desktop, but with the install program demands for resolution, it ain't gonna happen. Sorry, just venting. Corel just does not get the finer points).

 

[footpad]

jlockley,

Believe me, I fully understand about the frustrations of tech support. it's not an easy position and it's sometimes amazing that anyone gets anything accomplished via the telephone.

If you're running into a "looping" problem trying to install WordPerfect Office 8 (or Paradox 8, for that matter), you might see if

http://techtricks.com/assorted/winmess.php

helps you work through it.

Hope this helps...

-- Lance

 

[jlockley]

This is W2k, unfortunately. Apparently uninstalling the Version 10 can remove or corrupt the OBDC Drivers/Bde, which means that no version of Paradox could be used. This issue could be resolved by seeking up and (re?)installing bde 5.1xx from the Borland website.

After exhausting every trick I can imagine (fooling with permissions, attempting to set up a dummy address book, the obvious repeated installations and removals, the program still refuses to create the requisite Paradox address book. I know there is a way, but Corel's solutions are window dressing. This does seem to be a wide spread problem.

 

[footpad]

jlockley,

Hm. About the only other thing I can think of is to make certain you're logged in as Administrator, especially before installing the BDE updates.

Sorry, but I've not seen this and I've got four version of Paradox installed on my system right now (7.32, 8, 9, and 10).

I've had no problems getting them all to co-exist. About the only thing I do differently than most other people is that I install each version into a separate directory structure.

At this point, I'd suggest searching groups.google.com for additional ideas from the Usenet forums.

Sorry I can't be of more help on this one...

-- Lance

 

[jlockley]

Been there. Thanks for the suggestions, though. The administrative rights and permissions are not a function, but this is, actually, an office suite problem rather than a dababase problem. Paradox (both versions) works fine. The mess is the Word Perfect address book interface via Corel Central.
Just out of curiosity, do you find 10 substantially better than 8?

 

[footpad]

jlockley,

Ah, that must be it. I don't use Corel Central, as I heard there were vague problems with it and, well, I have other ways of tracking my addresses.

As far as whether or not Paradox 10 is "substantially" better than 8 goes, well, I would say so, but not perhaps for the obvious reasons. here's what I liked about the differences:

1. Corel ported Paradox from BCC to VC during the Paradox 9 phase. This resulted in some performance improvements and fixed a number of long standing memory leaks.

2. Paradox 10 includes two features I find really spiffy: 1) Runtime as part of the basic purchase and 2) StringLists. The former means I get both the interactive product and the redistributable one for the same price. While I haven't shipped a runtime app in a coule of years, I appreciate having it available for testing purposes.

StringLists are, essentially, text files containing integer identifiers for various string values. They help reduce menus, localization, and other such things. I'm still exploring their best uses, but they've certainly got some potential.

3. Corel did a *lot* of work trying to resolve the long outstanding problems with printing that appeared with Paradox 7.32; that work has gotten better through each iteration and service pack. I'm not convinced it's perfect yet, but it's much better than it was.

4. Paradox 9 added an ObjectPAL method for detecting corrupt tables. While not completely perfect, at least it's now possible to add code to detect the condition without using Delphi.

Having said all that, there are some things that have taken a step backward.

1. In Paradox 9, Corel rewrote the Create/Restructure dialog to use a different keyboard mapping. Personally, I find it far more difficult to use and time consuming than the previous iteraction.

2. It's harder to declare table aliases (monikers) in the current versions. There are some design tricks that I'm still trying to determine how to pull off in the latest.

For the moment, I'm dealing with both by doing most of my table manipulation in Paradox 7 and running the version I need after the tables (and data models) are created).

Hope this helps...

-- Lance

 

[jlockley]

It does quite a bit. Thanks.

 

[jlockley]

Let me add another one from the dummie's perspective. When designing a form in P8 (and probably 9) you could pull down and define a field object. In 10 you first create the field then you must define it. This does not always work. (but don't ask me why. I just remember the frustration, not the details.)

 

[jlockley]

Let me add another one from the dummie's perspective. When designing a form in P8 (and probably 9) you could pull down and define a field object. In 10 you first create the field then you must define it. This does not always work. (but don't ask me why. I just remember the frustration, not the details.)

I am reading through a few older posts after I apparently couldn't receive your mail. Your information read after the rush is enlightening. Thanks.