Microsoft test for Report Builder!!

rbuser

Hi All,

I have a program want to pass by Microsoft test for apply ISV/Software
competency. And it will use a program call Application Verifier for
testing. But my program has error message on call report builder preview
function. I try run your demo program for testing. (Under Delphi 5 & 7,
ReportBuilder 7.04, Windows XP Professional, Application Verifier 3.2 and
select default test). But I perform any report in this program have same
error message "External Exception 80000003". (Attached is the test log by
Application Verifier)

Hints:
Perform report in All Folders -> Sales -> Order Summary, it will have ten
times error message.
1. After run design mode to invisible all ppDBTexts in this report, it
haven't any error message return.
2. After disable test the heap will haven't any error message return.

I want to know the following:-
1. ReportBuilder 10.04 still have this problem?!
2. If this is not ReportBuilder problem, how can I to solve it?

Thanks,
Martin

Following statement capture in my testing result from Microsoft
Heap Use

Dynamic memory allocations come from the heap. Heap errors can result in
security

holes and can cause an application to fail. There are several invalid ways
to use the

heap, including:

Allocating memory but writing beyond the end of the allocation (buffer

overruns)

Using allocated memory after it is freed

Freeing an allocation twice

Freeing unallocated memory

Using wrong heap pointers


Demo program
C:\Program Files\Borland\Delphi5\RBuilder\Demos\3. EndUser\1. Report
Explorer\EndUser.dpr

Link for download Microsoft Application Verifier
http://www.microsoft.com/technet/prodtechnol/windows/appcompatibility/appverifier.mspx

nardmoseley

- we use a product called AQTime as part of our QA process. It can monitor
Delphi applications for memory leaks/resource leaks etc.

- Delphi 2006 includes a new memory manager (from FastCode) that can be used
to detect memory issues as well. The new memory manager also fixes some
memory management bugs that are present in prior version of Delphi - from
what I understand.

- Using a tool that knows about the Delphi VCL can be more helpful because
it can show you where in the code that issue might be (call stack).

- Fixing leaks is an ongoing battle that never ends- just like fixing bugs.
It is part of the software development process. The VCL is in flux and our
code is in flux. Both can have potential leaks. Also, printer drivers can
often leak. The Delphi IDE has leaks and I bet Visual Studio has leaks also.

- Customers that have tested RB applications using tools such as AQTime
report that overall RB is solid. They do from time to time send us tips
about places in the RB source code that have leaks and we incorporate those
changes in the RB source.

- You can add RBuilder\Source to your Delphi libarary path and use AQTime or
comparable tool to find where the issue are in the source code. (There will
not be any further updates to RB 7.x, but we are actively supporting RB 10.x
with updates/fixes.)


--
Nard Moseley
Digital Metaphors
www.digital-metaphors.com