How to work with SQL in a big application ?? Help !

[Nico Vanhaecke <Nico.Vanhaecke@ping.be>]

Hi,

I have an application where I have to build approx. 600 different queries. 
 I think 450 are view and select queries, 150 are updated queries.  What's 
the best way to work with so much queries
1.  Put for every sql-statement an component in a datamodule and every time 
you need an sql-statement take the right component.  Create thus, 450 
sql-comp and 150 update-sql-comp.  When you want to view the sql at screen, 
you have to create also for every component an datasource.  Is this the 
right way or give that enormous overhead.
2.  Create some workqueries and uses the loadfromfile command.  Create for 
example 50 workqueries and when you need an sql-statement, use one that 
isn't in use.  Is loadfromfile not slowly when you have to take file from a 
server, anywhere in the network.
3.  Create everytime an sql-component at runtime, and destroy it when you 
are finished.  No components in the data-module.

What's the best way.

BTW, is it possible to build an application with 200 open tables and at 
least 100 different forms  ?

Thanks in advance,


Nico Vanhaecke.