I have found the same thing in a Union Query where the same parameter name
is used each side of the Union TADOQuery creates 2 parameters with the same
name. Further, I find that if I populate the query statically at design
time, the Q performs as expected BUT
If I populate the SQL text at run time
SQL.Clear; SQL.Add(') etc etc then
SQL.ParamByName('P').AsInteger := :P
then the query behaves in an unpredictable manner.
For the moment I am working around this by giving different Parameter names
for each side of the union query and loading the parameters seperatly at run
time.
Is this behaviour normal for ADO ??
Cheers...
-----Original Message-----
From: Neven MacEwan <[EMAIL PROTECTED]>
To: Multiple recipients of list delphi <[EMAIL PROTECTED]>
Date: Tuesday, 9 November 1999 3:45 PM
Subject: [DUG]: TADOQuery
Hiya All
I've just found that if you use the same parameter name in a TADOQuery twice
it creates 2 Parameters (not 1 like a TQuery)
Is this a bug or a feature?
Any comments - who do I approach if its a bug
Regards
Neven
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
