Mark
Re your prposed methods
>> 1. Just like a TTable, with a Select * from MyTable in the SQL property
(at one extreme);
Simple port (but doe nothong for your bandwidth problem)
>> 2. As a purely open Query with nothing in either parameters or SQL,
relying on code supplied by the app at runtime. In this case one >> TQuery
could be used to access several files at different times.
Can't really see the point in this, makes the whole app programatic (which
it isn't currently)
>> 3. With both SQL and parameters specified at design time, in which case
the TQuery is for a predetermined purpose ( and attached >> to a specific
file).
This is what I'd do (and it is close to your current design philosophy),
re the 'util' query it is so easy to do this programatically I'd do that
(especially for non data returning queries)
with TQuery.Create(nil) do
try
....
finally
free
end
Note with paramters using statis substitution (as Donovan suggested with
ReplaceString) is not as efficient
as TQuery parameters (when using the 'same' query multiple times) as the
query is compiled multiple times
Tho in practice I don't worry about this.
Re master details I have a component (TRelationship) which links datasets
and has a propagation delay in it (which
vastly cuts down the load on the server (Email me directly if you want the
source)
HTH
Regards Neven
N.K. MacEwan B.E. E&E
Ph 649 574 0027
Fax 649 570 2706
[EMAIL PROTECTED]
"A truth denied the light of action will wither to a promise, propaganda and
then a lie"
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe delphi"
