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

AV in TppListView.WMNotify

edited June 2002 in General
Hi,

I've spent hours trying to find why, but I got a serious problem here...

I create my RB object in code like this :


report:=TppReport.Create(Self);
ReportDesigner:=TppDesigner.Create(Self);
ReportDesigner.Report:=TppReport(pObject);
ReportDesigner.DataSettings.SessionType:='dbExpressSession';
ReportDesigner.DataSettings.DatabaseName:=pDatabaseName;
ReportDesigner.DataSettings.DatabaseType := dtInterbase;
ReportDesigner.Show;

When I got to the Data tab, select File/New and Query designer, I got an AV
like EAccessViolation with message 'Access violation at address 77E778DA in
module kerlen32.exe at the begining of TppListView.WMNotify

I'm running on Windows XP, my database is Interbase 6.01 with DBExpress
driver

Thanks,

Pascal

Comments

  • edited June 2002
    Hi again,

    I probably found where the AV come from... it occur only when I include the
    XP Manifest in my project (to work with XP Theme).

    Perhaps there is a bug between your components and XP comctl ?

    Regards,

    Pascal

  • edited June 2002
    Yes, it is the XP manifest. Here is an article I found
    http://delphi.about.com/library/bluc/text/uc111601a.htm

    At the bottom it states

    "Warnings
    Microsoft warns all developers that they have in fact eliminated a lot of
    the support code in the comctl32.dll library, and that you should always
    test thoroughly to ensure all aspects of your controls work properly before
    distribution. It has been my experience that there are in fact some
    compatibility issues with Delphi. So far, the only discrepancy I have found
    was in the TListView component. If you use the TListView component with the
    view style of vsReport, you run into a problem using the TColumns property.
    During runtime, you will generate a kernel error if you attempt to use
    column headers with said view style"

    We rely on the TListView as an ancestor. If TListview doesn't work then
    we're currently out of luck on this one. Thanks for letting us know about
    the issue. We haven't yet tried taking this approach to distributing to XP
    before so we never received the error before. For now you'll have to build
    without the XP Manifest.

    Cheers,

    Jim Bennett
    Digital Metaphors

This discussion has been closed.