Home General
New Blog Posts: Merging Reports - Part 1 and Part 2

RB 6.03 - Unable to OPEN Report Components

edited October 2002 in General
I delivered source code to a client developed originally in Delphi 5, RB
6.03. The client installed in a Delphi 6 environment using RB 6.03 and they
are unable to successfully open the Report Components created in my
environment. I finally upgraded my system to D6 and cannot duplicate their
problem.

The differences between our environments are:
1. They are running NT4 SP6 and I am running W2k.
2. They are using RB Professional and I am using RB Enterprise (no
Enterprise features are being used that I am aware of).
3. I have administrative rights in my environment, they do not.

They can drop a component on a new form and open successfully. The problem
exists only for the previously created components.

Any suggestions?

Comments

  • edited October 2002
    It's not a long shot, but make sure that there is a printer installed and
    that it has the latest printer driver. What is their default printer? If
    that checks out, try installing a different printer driver. The problem may
    be that when the report designer is launched from the delphi form, it might
    not be able to successfully talk to the printer driver. RB uses the printer
    driver to help measure text width in order to help you design a report for
    the selected printer in the report's printer setup property.

    The RB 6.03 installs are created at the same time and should have the same
    dcu and bpl footprints. You should be able to move from your machine to
    your client's with no problem. Another problem might be that one
    installation is corrupt, using older bpls or dcus. Please follow the
    corrupt installation cleanup procedure to make sure that there are no old RB
    files on either machine.

    If none of this helps, then can you send us an example component and we'll
    try to load it on our RB 6.03 D6 installation with no administration rights
    as a user and using hte same default printer as your client is using.
    Administration rights shouldn't matter, unless you are unable to access the
    RBuilder.ini file in the windows system directory.

    --------------------------------------------
    Article: Cleaning up a Corrupt Installation
    --------------------------------------------

    If you have been advised by Digital Metaphors technical support that you may
    have a corrupt installation, or if you are having difficulty installing,
    compiling or running applications after a ReportBuilder install, then it may
    be necessary to manually remove all ReportBuilder files from your system.
    Corrupt installations usually result when you are installing over a previous
    version of ReportBuilder which was not installed into the default directory,
    which was recompiled from the source, or when ReportBuilder files were
    manually moved from the default install location. Cleaning up a corrupt
    installation, consists of locating all ReportBuilder related files, and
    deleting them from your system. The first step is to use the uninstall
    program to remove as much of ReportBuilder as possible.


    Run the uninstall program

    1. Exit Delphi, and all other applications. You should have no applications
    running except the uninstall, otherwise you may lose some of your work.

    2. Select Start | Settings | Control Panel from your Windows desktop.

    3. Double-click the Add/Remove programs icon.

    4. Locate the version of ReportBuilder you wish uninstall and double-click
    it.

    5. The first page of the Uninstall Wizard allows you to choose between an
    Automatic or Custom uninstall. Choose Custom and click the Next button.

    6. Click the Select All button, then the Next button. Repeat these steps
    until you reach the last page of the wizard.

    7. Click the Finish button. All of the items you selected will be removed
    from the system.

    8. After all the ReportBuilder files are removed, you may be prompted to
    reboot the system. If this is the case, reboot the system.


    Delete the ReportBuilder root directory (and all subdirectories)

    1. Using the Windows Explorer, locate the ReportBuilder root directory. The
    default directory is:

    C:\Program Files\Borland\DelphiX\RBuilder

    2. Once you have located this directory, inspect it. If you have any custom
    work in this directory which you would like to keep, move it to another
    directory.

    3. Delete the ReportBuilder root directory.


    Delete all remaining ReportBuilder files

    1. Using the Windows Explorer, search the entire hard drive for all
    occurrences of:

    dclRB*.bpl
    dclRB*.dcp
    rb*.bpl
    rb*.dcp

    2. Delete any occurrences which correspond to the version you are removing.
    All packages are named with the convention NN, where the first number
    is the ReportBuilder version and the second number is the Delphi version.
    Thus, a typical package name for Delphi 5 would be rbRCL45.bpl. The same
    package for Delphi 4 would be: rbRCL44.bpl. Check Installing ReportBuilder
    for a list of the packages associated with each version.

    3. Using the Windows Explorer, search your hard drive for all occurrences
    of:

    pp*.*
    da*.*
    ra*.*

    4. These are the prefixes used by individual ReportBuilder units. 'pp' is
    used for ReportBuilder units, 'da' is used for DADE units, and 'ra' is used
    for RAP units. Depending on which ReportBuilder you have (Standard,
    Professional or Enterprise) you may not have all of these unit types.



    Additional Notes

    1. Never have Delphi running when installing ReportBuilder.

    2. All ReportBuilder related files should be stored in the root directory
    $(DELPHI)\RBuilder.

    3. All ReportBuilder run-time packages should be stored in the
    Windows\System directory.

    4. You should never have ReportBuilder files in Delphi\Lib, Delphi\Bin or
    Delphi\Projects\Bpl.

    --
    Tech Support mailto:support@digital-metaphors.com
    Digital Metaphors http://www.digital-metaphors.com


    Cheers,

    Jim Bennett
    Digital Metaphors

This discussion has been closed.