Home› General
ReportBuilder 22.06 now available including Delphi 12.2 support!
New Blog Posts: Merging Reports - Part 1 and Part 2

"A component named ... already exists" error

rbuserrbuser
edited July 2001 in General
I report a VERY odd problem in a Delphi 5 application with ReportBuilder
5.56: In all four computers I can get my hands on, the application works OK
(they have Windows ME and Windows 98 v2). In my client's PCs, however, the
program does not load past the Splash screen with the error "A component
named Transaction - Number already exists". Their two computers run under
Windows 98 v2 and Windows 95 (and the error is the same in both).

Although the name "Transaction - Number" is logical within the application,
I do not recall using it, and I definitely cannot find anything resembling
it in the source code (written 100% by myself).

This error is driving me crazy, and I cannot visit the client's location
since they are overseas. As stated earlier, I have not been able to
reproduce the error in any of my computers.

To compound the puzzle, this error surfaced with the current version 8.1.4
of the application. However, when the client reinstalls an earlier version
(8.1.2) the error appears! (and it did not appear in the original
installation of version 8.1.2)

Please offer me any pointers -- I have run out of creativity on this one . .
.

THANKS!

Best regards,
Ray

NOTE: I suspect the error relates to ReportBuilder, but I cannot be sure.

Comments

  • rbuserrbuser
    edited July 2001
    Hi Ray,

    Are you loading report templates on startup?
    Is your startup client depending (e.g. loading the last opened report)?
    Have you checked your DFMs and RTMs for any occurence of 'Transaction -
    Number'.
    Do you naming some components by code?

    regards,
    Chris Ueberall;

    OK
    application,
    .
  • rbuserrbuser
    edited July 2001
    Chris:

    Yes! I found the darned error thanks to you. In effect, the Data Module has
    a "Transaction-Number" index defined over one of the tables and this
    apparently caused the error because I modified the data definitions (I
    guess) and/or the user did not install data correctly.

    Anyway, now I have a path to follow. THANKS!

    Best regards,
    Ray

    Note: As it happens, the error had nothing to do with ReportBuilder -- Sorry
    guys . . .

This discussion has been closed.