Problem using datamodules
I have only just purchased RB Pro (6.03) and am using it with D6 (Update
pack 1) on W2K (SP2), and have a problem, which I have managed to track down
when it happens but not why:
I have a datamodule where my IBClientDataSets are. Originally, I had all my
RB components on here apart from the report itself, which is on the report
form. When the form is destroyed, the application hangs.
I have now created a test form, with just the report and a button which
calls the print method. This also hangs the application when the form is
destroyed.
I then moved the ppDBpipeline component to the form. Same problem.
I then moved the datasource to the form. Same problem.
I then moved the ClientDataset for the form, and it works fine.
So, is it something I am doing (or not doing) that is causing this, and if
so, can someone give me any advice?
I also get an annoying crash when the report is printed, where it stops at
ntdll.dbgUserBreakpoint, which I think is something to do with the debugger
and Win2K, but I'd like to find out how to stop it, as it rather spoils my
RB experience (and I have just switched from another product and am so far
VERY impressed!)
Regards
Jeremy Knowles
pack 1) on W2K (SP2), and have a problem, which I have managed to track down
when it happens but not why:
I have a datamodule where my IBClientDataSets are. Originally, I had all my
RB components on here apart from the report itself, which is on the report
form. When the form is destroyed, the application hangs.
I have now created a test form, with just the report and a button which
calls the print method. This also hangs the application when the form is
destroyed.
I then moved the ppDBpipeline component to the form. Same problem.
I then moved the datasource to the form. Same problem.
I then moved the ClientDataset for the form, and it works fine.
So, is it something I am doing (or not doing) that is causing this, and if
so, can someone give me any advice?
I also get an annoying crash when the report is printed, where it stops at
ntdll.dbgUserBreakpoint, which I think is something to do with the debugger
and Win2K, but I'd like to find out how to stop it, as it rather spoils my
RB experience (and I have just switched from another product and am so far
VERY impressed!)
Regards
Jeremy Knowles
This discussion has been closed.
Comments
I've reproduced this problem in D6 with RB 6.03. Until we've found a work
around, I would put all of the data access components on the form.
debugger
Try shutting down Delphi and running the EXE by itself. Microsoft left some
debug breakpoints in the DLLs and the dialogs (particularly the Print
dialog) seem to trigger these. If the problem goes away in the stand-alone
EXE then that's what it is. We don't know of a workaround for it, though
perhaps there is a service pack for Win2K which cleans these up?
--
Tom Ollar
Digital Metaphors Corporation
http://www.digital-metaphors.com
info@digital-metaphors.com
feel free to contact me by e-mail so I can try it, since I now must
duplicate the datasets I need from my datamodule into my report form, which
I'd like to remove as soon as I can.
As for the debug breakpoint one, it doesn't happen in the exe, so I suppose
I just hope that SP3 will resolve the problem, whenever it comes along.
Regards
Jeremy
links to the datamodules, and still I have the problem. Can you advise what
it might be, so I can stop the crash, as I want to ship my application this
week.
Regards
Jeremy Knowles
arrives...