recommended pre-update and post-update steps 4.0.7 -> 4.1.1, BCB3 on WinNT Server

[PColbert]

When things go wrong under WinNT, starting over can be difficult; especially with a large number of BCB add-in components installed. So I prefer to be pro-active, and gather information needed to prevent problems, rather than have to restore from backups and start over.

From prior DOA installations, I remember that the installer is quite nice, and does a lot of work for the developer. However, there is always a line between what the installer does during installation, and what the developer should do before and after running the installer.

The big problem is that different vendors, and different installers, draw that line differently. What's "obvious" to one is decidedly not "obvious" to the next one. Therefore, it is important, in each case, to document that dividing line somewhere, especially the developer's recommended before-and-after steps, both on a per-installation and per-project basis.

Even if there are no such steps, it is important to document that there are none. Otherwise, the prudent developer keeps looking for that (omitted) information.

Alas, no instructions appear to be available for study before actually running the installer. (I saw no downloads for any documentation. Did I miss something?) Hence, if there are any documented pre-update steps that I should do, before running 4.1.1's installer, I can't read about them.

From previous notes, I have the following:

0. Back up everything, of course.

1. Whichever Windows account normally uses BCB3, temporarily give it Admin privileges, so that it can run the installer. (Running it under a different account may not correctly update BCB3's menu and/or palette, as seen from the normal account.)

2. Open BCB3, and close all open projects. (Otherwise, BCB3 itself may not start, after the installer is finished.) Close BCB3.

Are there any other pre-update steps I should follow?

For example, should I uninstall DOA 4.0.7's TOraclewwDataSet? Or will the installer update it for me?

For existing projects that use DOA 4.0.7, are there any pre-update steps I should follow?

Post-update, my notes indicate the following:

1. Open BCB3, and verify that the Palette and Main Menu items appear as expected.

2. If the correct TOraclewwDataSet is not installed, install it.

3. Close and re-open BCB3.

4. Verify that that the correct TOraclewwDataSet is installed. Close BCB3.

5. Revert the Windows account to its original (non-Administrator) status.

6. For each project that uses a DOA component:
a. open that project,
b. open every Unit that references a DOA component. (This give the new DOA the opportunity to modify every .dfm file it may need to modify.) (This is why the project should be backed up first.)
c. Recompile and re-link the entire project.
d. Save the project.
e. Test the resulting executable or library.

Regarding post-update steps, do I have too many steps? Too few? What steps have I missed?

-Phil

 

[Marco Kalter]

There are really no pre- or post-update steps involved, the installer will take care of removing the old files, installing the new files, and registering everything in the IDE.

Backing up your projects (if you don't have it under source control) is always a good idea before any update of course.

Recompiling components and packages that use Direct Oracle Access is the only post-update step that is required.

 

[PColbert]

I've applied the update, with the following results:

. pre-update step 1 proved unnecessary. The installer ran without any Windows account adjustments.

. Based on past experience, I'd already done pre-update step 2. It wasn't worth the risk.

. The installer removed 4.0.7, including 4.0.7's TOraclewwDataSet, but not completely. On startup, BCB3 complained that it couldn't find "doa40c3.bpl" and "doa407ww.bpl". I believe these errors could have been avoided entirely, but since they appear to be recoverable (just click "OK" and "No", respectively), it would be sufficient to just document them.

. post-update step 1 is just common sense. It proved necessary, when it clearly showed that TOraclewwDataSet had disappeared from my Palette. The 4.1.1 installer did not update this component after all. Thus, post-update step 2 also proved necessary, making post-update steps 3 and 4 only prudent.

. When performing post-update step 2, be prepared to search for one or more .bpi files.

. post-update step 6b proved unnecessary. I was able to recompile and relink without visiting every single DOA-using module in my project.

At this point I would not suggest any changes to your installer, only its documentation, so that users of the installer know as much about what to expect (from applying updates) as you do.

Also, it is only prudent to make the installation instructions available in advance. I found them, on my hard disk, only after running the installer, as part of the installed documentation. If there's a copy on-line, available for reading before running the installer, I'd be delighted to learn of it.

Software configuration (installation/removal/configuration of components) tends to be ad-hoc, fragile, inflexible and unforgiving. That is, recovering from mistakes tends to be difficult, painful, and expensive. In one case (not today, thank goodness) I've had to uninstall 15-odd add-ins, then BCB3, and then re-install them, just to get a clean slate for installing some other BCB3 add-in. That's half a week, gone!

So an ounce of information goes a long way. It helps people feel confident that they know what they're doing -- and that you do, too.

-Phil