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

AV when encapsulate the report in dll

edited January 2009 in General
Hi, all,

I encapsulated the report into the dll under D7, it seemed work fine
except for throwing out the AV when exist from the exe application. I
passed the ADOConnection object the dll.

The exception says: project1 raised too many consecutive
exceptions:'access vailation at 0x006237ea: read of address 0x011c0d9c'.

What is the wrong with my codes?

Regards,

Jak



--- posted by geoForum on http://delphi.newswhat.com

Comments

  • edited January 2009
    Hi Jak,

    What are you ultimately trying to accomplish with your application? Unless
    you are trying to call your report from another environment we recommend
    using the Delphi package architecture rather than dll's.

    Are you able to get the .dll example functioning correctly? This example is
    located in the \Demos\7. DLL\... directory.

    --
    Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com

    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
  • edited January 2009
    Hi, Nico,

    Thanks for your reply.

    What I want is to seperate the invoice printing module from the
    application to dll, so I could customize it without modificating the
    application.

    Yes, I took a look into the demo application under the \7.dll\
    directory, but it would still encounter the Runtime error 216 when I
    changed the datasource to ADOTable, even though I dropped an
    ADOConnection on the dll form. If I removed those ADO components all,
    the application would work fine. It seems out of order when using ADO
    components.

    Regards,

    Jak





    --- posted by geoForum on http://delphi.newswhat.com
This discussion has been closed.