Problem with removing or deleting components from Report Designer

rbuser

I'm not sure if this already known but I have been victim to this enough
times to want to mention it in the newsgroup.

In Report Designer, if I have a component on a which makes use of a calc
method (for instance) defined using the calc tab and I delete the component
from the Designer (forgetting to first delete the calc method) I am unable
to save the unit in which the report is defined. This does not apply with
events coded outside the Designer - they remain in the code and can be
deleted separately.

If I make sure that the method is deleted first, then the component there is
of course no problem.

It's extremely annoying because it usually occurs after I have done some
major refurbishment to the report and need to save - find I can't and lose
the work doen.

Is there any way to account for this when deleting the component from the
report canvas - either issue a warning that there are routines attached to
the deleted component or just silently removing them behind the scenes?

cheers - David

digitalmetaphors

This is not a known issue. Are you using RB 7.02? Are you using Delphi 1-5?
If you are using Delphi 1-5, then do not place a report component on a
TDatamodule.


Cheers,

Jim Bennett
Digital Metaphors

rbuser

Hi Jim,

Sorry, I should have mentioned my setup. In the situations I'm reporting I'
either using Delphi 7 Enterprise or Delphi 6 Enterprise both with Report
Builder 7.02. However I *am* placing the report component in the
DataModule.

Should I move the component either (1) back to the main module or (2) into
its own module (which would probably open up another can of worms)?

I'll try moving it out of the datamodule in any case but that means I have
to "doctor" a whole raftload of apps since this has been my adopted m.o.
unless you can suggest something else.

Good luck with the move! Are you by any chance moving into the offices
abandoned by TurboPower? :=))

cheers - David

digitalmetaphors

It should work correctly in a datamodule in D6 and D7 and RB 6 and RB 7.
Maybe just this one report is showing a problem and we may be able to fix
it. However, if you test with this report in a TForm just to see if the
problem goes away, then please send us an example in a TDatamodule where it
shows the problem or tell us how to reproduce it with a sequence of steps
using one of our demo reports in a TDatamodule in the RBuilder installation.
Send it to support@digital-metaphors.com

Thankyou for the kind wishes on the move. I'm looking forward to living by
the mountains. I believe TurboPower was based out of Colorado Springs. We're
moving to North Denver (Interlocken area just south of Boulder) :-)


Cheers,

Jim Bennett
Digital Metaphors