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

Getting closer to update problem

edited June 2002 in General
Here is the sql that 6.03 is generating from one of my created reports :

SELECT
MEMBERS.UID,
MEMBERS.ACCOUNT_NUMBER,
MEMBERS.HOME_CLUB,
MEMBERS.MEMBER_NUMBER, MEMBERS.FIRST_LAST, MEMBERS.FIRST_NAME,
TRANSACTIONS.HOME_CLUB,
TRANSACTIONS.DATA_ENTRY_CLUB,
TRANSACTIONS.DATE_TO_APPLY,
TRANSACTIONS.DATE_ENTERED,
TRANSACTIONS.TIME_ENTERED,
TRANSACTIONS.DESCRIPTION,
TRANSACTIONS.PAYMENT_METHOD_1,
TRANSACTIONS.PAYMENT_METHOD_2,
TRANSACTIONS.CHARGE_AMOUNT,
TRANSACTIONS.PAYMENT_AMOUNT,
TRANSACTIONS.ADJUSTMENT_AMOUNT,
TRANSACTIONS.EURO_CHARGE_AMOUNT,
TRANSACTIONS.EURO_PAYMENT_AMOUNT,
TRANSACTIONS.EURO_ADJUSTMENT_AMOUNT,
TRANSACTIONS.RECEIPT_NUMBER,
TRANSACTIONS.COMPUTER_NAME,
TRANSACTIONS.QUANTITY
FROM MEMBERS MEMBERS
INNER JOIN TRANSACTIONS TRANSACTIONS ON
TRANSACTIONS.MEMBER_ID = MEMBERS.UID
WHERE ( TRANSACTIONS.PAYMENT_CURRENCY <> 'EURO' OR
TRANSACTIONS.PAYMENT_CURRENCY IS NULL ) AND TRANSACTIONS.DATE_TO_APPLY >=
'01/19/2002' AND TRANSACTIONS.DATE_TO_APPLY <= '12/19/2002' AND
(TRANSACTIONS.ITEM_NUMBER <> '9936' AND (TRANSACTIONS.ADDON IS NULL) OR
(TRANSACTIONS.ADDON = 'F')) ( ) ORDER BY
TRANSACTIONS.COMPUTER_NAME,
TRANSACTIONS.DATE_TO_APPLY

Notice the ( ) before the order by instead of around the join...hmmm...what
is causing this?

Comments

  • edited June 2002
    Fixed...my error. I was creating the sql at run-time and obviously screwed
    it up.

  • edited June 2002
    Hi Stacey,

    for the future, could you please keep those messages in one thread, thanks.
    (I see 4 threads belonging to the same problem)

    regards,
    Chris Ueberall;
  • edited June 2002
    Sure, but, could you maybe answer them. My product is down now because I
    chose to update to the latest version of RB. I realized that I was using
    the wrong demo, so I opened Demos/4. EndUser Databases/Interbase/1. BDE.
    Ran the script and still, when I go to create data there are no tables to
    choose from.

    I am trying to work on this problem myself, but none of the demos seem to
    work correctly and my customers are not going to be happy if I can't update
    them.

    Any help would be greatly appreciated.

    Stacey




  • edited June 2002
    Is the DataType field necessary? That is the only difference I can see at
    this point. I don't have that field in RB_FIELD...I have DataType currently
    set to FIELD_NAME.

  • edited June 2002
    Another error I forgot to mention is on loading of Delphi.

    The procedure entry point
    @Ppclass@TdaDataView@SetEnabledOptions$qqr51System@%Set$t23Pptypes@TppDataEd
    itType$iuc$0$iuc$8% could not be located in cynamic link library
    rbRCL55.bpl.

    Cannot load package c:\winnt\system\rbADO55.bpl

    Is this relevant?


  • edited June 2002
    And, if I do need to populate the DATATYPE field, what are the values that
    can be listed in this field?


  • edited June 2002
    Stacey,

    see RBuilder.hlp 'TppDataDictionary Component'.
    The 'DataType' field contains the field types as strings.
    Linking 'DataType' to 'FieldName' sounds strange for me.

    regards,
    Chris Ueberall;

  • edited June 2002
    Yes, there are probably two bpls with this name on your machine, and each is
    a different version. Follow the corrupt installation cleanup procedure to
    make sure you don't have any other duplicate ReportBuilder files on your
    machine.

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

  • edited June 2002
    You can also temporarily disconnect the data dictionary to simplify the
    problems to solve in your configuration.


    Cheers,

    Jim Bennett
    Digital Metaphors

This discussion has been closed.