Fast Reports DLL Problem
Hi guys,
this message is really for the FR guys themselves.
I emailed an example, description and instructions on the 30/07. then sent another email on the 12/08 asking for confirmation that the FR team recieved my first email. I still have not had a reply.
Setup : SQL Server 2000, Delphi 6 Pro, Fr 2.53
The Bug :-
I used the example DLL source and added the frADO components. I then wrote a simple report using the "master" database in sql server. I make the report raise an exception on one of the bands by assigning an undeclared variable to its self
e.g. x := x + 1
this raises the exception and all is fine, but when i exit the fastreports DLL and then exit the parent program. I recieve lots of Memory address errors. Even if i tried to do something else in the parent program instead of exiting it would crash with these errors.
I need an answer to this as the Reports system is in 2 of out major products and we are due to start supplying lessons on how to use it very soon. With a bug like this, that makes the system look unstable it doesnt look good for our reputation
Any help greatly appreciated
Steve
this message is really for the FR guys themselves.
I emailed an example, description and instructions on the 30/07. then sent another email on the 12/08 asking for confirmation that the FR team recieved my first email. I still have not had a reply.
Setup : SQL Server 2000, Delphi 6 Pro, Fr 2.53
The Bug :-
I used the example DLL source and added the frADO components. I then wrote a simple report using the "master" database in sql server. I make the report raise an exception on one of the bands by assigning an undeclared variable to its self
e.g. x := x + 1
this raises the exception and all is fine, but when i exit the fastreports DLL and then exit the parent program. I recieve lots of Memory address errors. Even if i tried to do something else in the parent program instead of exiting it would crash with these errors.
I need an answer to this as the Reports system is in 2 of out major products and we are due to start supplying lessons on how to use it very soon. With a bug like this, that makes the system look unstable it doesnt look good for our reputation
Any help greatly appreciated
Steve
Comments
in some cases the var x must be initialized to a value first.
ie: empty string or number, depending on what it will be used for.
thanks for the reply, but i know that i have to add a value to the variable before assigning the variable to itself. What I want to know is, why does it cause the parent program to become unstable and crash when i exit the report writer.
It works if i have FR in a exe, but as a dll its unstable
Come on FR Team, I still havent had 1 single reply to my emails yet