FastReports w/ tree tier solution

[Guest]

I am going to start by quoting @Wloochacz from another thread:

 

Quote

In general, this is true, especially in SQL executed on the server side, such as stored procedures, triggers, etc.

And there, it's better to write like this:

select
   A.*
from foo1 A
inner join foo2 B on (A.ID = B.ParentID)

instead of this:

select
   A.*
from foo1 A 
where A.ID in (select B.ParentID from foo2 B)

Although the result will be identical.

However, in some cases it is simply convenient.
For example, in my application I pass an array of PrimaryKey values to ReportManager so that he can ask the server for the data he has selected on the list.

It works like this:

 

And where in SQL looks like this:

where TD.IdDevice in (10,12,16,23)

Simply clever 😛

I have been using FR for a very long time. In some implementations i have used the "live" functionality like drill-down and some of my users really appreciate the "edit report" functionality.

I am currently pondering wether to produce the reports on the server or on the client.

Server it's obvious that things will be faster (mostly) and i could also benefit from using the exact same code for my REST server (web).

Client-side would probably deliver more of the "live" functionality. It will probably be easier to provide "click to lookup" functionality.

 

@Wloochacz, did you use drill-down, report editing and other similar stuff? It looks like you send the prepared fr3-file to the client. Is that correct?

Regards and TIA,

 

/Dany