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

A class named TraTppPrinterSetupRTTI already exists

edited January 2002 in General
When I put a MDI form in a .dll and build it with the vcl50.bpl (to share
the application object)
every thing works as expected. Until I place a TppDBPipeline component on my
child form.
I then get the message: A class named TraTppPrinterSetupRtti already exists.
I think this is because some where in the units I use there is in the
initialization section a line as follows:
RegisterClasses([TraTppPrinterSetupRtti]);

Is this a known problem and what can I do about it ?

Comments

  • edited January 2002
    This isn't a known problem. Do you have any RB source built into the .dll?


    Cheers,

    Jim Bennett
    Digital Metaphors


  • edited January 2002
    I put a few MDI child forms in a .Dll.
    When ever I drop a Tpp component on it I will get this A class named
    XXXX already exists
    .
    I guess this is because the main application has a few reportbuilder
    components and the form in the dll also. They are both build with
    vlc50 package only. So I guess when the initialization section is run
    for the second time (first for the main app then the child) they
    collide in the application with the class which is already registerd
    by a RegisterComponents call.

    I'm not a component builder (you guys are way to good) but could it be
    better to put RegisterComponents calls in a separate unit and contain
    it only in the design package?
This discussion has been closed.