Another Server crash, but with no TeeChart

rbuser

Here is the call stack (if any use)

TTimer.WndProc((275, 1, 0, 0, 1, 0, 0, 0, 0, 0))

StdWndProc(1114778,275,1,0)

TApplication.HandleMessage

TApplication.Run

SDW_RBServer_Tree



Thx

nardmoseley

The call stack is not really very helpful.

We really need an example that we can run. Or if you can duplicate the issue
with our demo apps.

For debuggins, one option is to run the report server as a Delphi
application under the Delphi debugger and set it up to break on Delphi
exceptions.

Another option is to use a tool such as CodeSite. (Although we found thread
safety issues with CodeSite that we had to work around).


--

Thanks for supporting ReportBuilder! Please vote for ReportBuilder in the
Delphi Informant Readers Choice awards!

http://www.delphizine.com/ballot2004/

rbuser

Nard,

I understand your remark but honestly, last time i spend 2 days on
making a demo-app, on your data that also provoces a crash, i
couldn't make it crash. In my 'own' environment, with access over ADO
to Sql-server i could make it crash instantly. This makes me very
pissed of on computers in generally. I understand that you can't re-
create every clients environment at your office. But i did send you a
small SqlServer DB that had to be atteched to any SqlServer and then
you could see the crash. Your policies where that it had to be with
the default data.

It might be that some of the 'crash-reasons' could be due to some
special ADO stuff, of reports stored in a table, i don't know.

But, as last time i couldn't make it crash on normal data i'm not so
very fund of retrying to make a crashing demo again.

And i know that it has nothing to do with my code, as there is no
delphi code, except the basic code needed in a server to run. All my
code and data-access is in DADE and RAP.

I was running in a 'debug' mode, else i couldn't have giving you the
call stack.

Kind Regards.

nardmoseley

Its frustrating I realize that. We have many customers using ADO and SQL
Server successfully to build report servers. If you think you have a bug in
ADO, then try creating an example that uses ADO and MS Access data. You can
use the MS Access Northwinds data or you can create an MS Access database. I
think if there was a critical error in ADO we would know about it, but I
cannot never be 100% positive, perhaps you have encountered something that
others have not. There is no code in RB Server itself that is specific to
ADO. The only code specific to ADO in all of ReportBuilder is encapsulated
in daADO.pas - the DADE plug-in for ADO. The only functionality RB uses is
very basic methods of Delphi's TDataSet.

In general if the report can run in a standard Delphi application without
crashing, then it can run within the context of RB Server. The biggest
difference is that on the Server you have the issue of thread-safety.





--

Thanks for supporting ReportBuilder! Please vote for ReportBuilder in the
Delphi Informant Readers Choice awards!

http://www.delphizine.com/ballot2004/