ressourcenproblem under Windows 98

rbuser

I have a very large MDI Childform, over which I call the ReportBuilder with
the help of a Buttons at run-time. Under Windows 98 system resources are
then immediately exhausted and I must the program or the computer again
start. Who knows advice?

Best regards

Dirk

digitalmetaphors

Are you using RB 7.02 for this MDI app? Win9x systems do not handle
resources very well. Can you run our demo projects on this machine? Does our
MDI example (look in our installed demos directory) run on this machine?


Cheers,

Jim Bennett
Digital Metaphors

rbuser

Hi Jim,

I use the RB 7,02 and develop with delphi 6 enterprise Build 6,24 updates
luggage 2. The demo projects including MDI run without problems.
However also my MDI Childform needs very much resources, since it contains a
large PAGE control with many Win controls.

Best regards

Dirk

digitalmetaphors

The use of TPanel objects has caused resources problems in Win98 machines in
the past when a bunch of them are used. There are a few in teh standard
preview form of RB. One test you can perform is to use a custom RB print
preview form replacement that is lightweight in regards to visual controls.
Try placing just a viewer on a form that responds to left mouse clicks for
Viewer.NextPage and rigght mouse clicks for Viewer.PriorPage. That would be
as lightweight as I can imagine. There is a replacement form example in the
RB tutorials install directory. Search for rbPrvDlg.pas for an example of
replacing the form class. This is a visual way to replace the preview form.
However, this is only to test the preview form, not the preview from the
design Preview tab. There is the alternative which is to replace the
TppPreview plugin. The plugin is the code based way of replacing the
controls that are created in the preview form and the preview tab of the
designer. If you want to replace the preview in the report designer, then
replace the TppPreview plugin class. Here is an example of custumizing a
TppPreview descendent. You'll want to descend from TppCustomPreview and
create the minimum to support what you modeled in the custom form
replacement technique you did visually. Don't forget to unregister you form
replacement class when you decide to use a plugin replacement, otherwise,
you'll only see your changes in the designer and the custom preview form
will still show in the print preview form:)
http://www.digital-metaphors.com/tips/AddControlsToPreview.zip



Cheers,

Jim Bennett
Digital Metaphors