d> The idea is launch reports from the App. I'm thinking to use only
d> the ODBC driver to launch reports.

That's how I am doing it, and it works very well for me.
New applications generally are using ADO.net and the .net Provider for Firebird. I am restructuring all reports to use ADO.net DataSets as Source.
Because I am only a part time developer, I can not change all the reports at once, but must do it one by one.

So, basically:
Working on the data is done by applications written in C# using ADO.net 4.0 and some older stuff still (don't beat me *g*) using the BDE. Reporting using CR is done via ODBC, still using ODBC driver 1.0.2.0070 on 32-Bit clients, ODBC driver 2.x on 64-Bit clients.

Works PERFECTLY!

If you feel uneasy about opening additional and probably uncontrollable access paths to your databases, you can specify that DSNs must only be created in read-only mode.

I can offer to share some expertise or experience with you on that topic, but this list is probably the wrong place for it.


---