Richard


You're definitely into the seriously weird territory now! I look forward to the demo app.

Roy Lambert [Team Elevate]

I tried creating a small application to demonstrate the above behaviour.

* Created a new database with new application
* Existing database with the new application
* Existing database with existing application using a new form

In all cases, the offending clause below that was returning NULL is now returning the correct result.

SELECT
  parentID,
  (SELECT C1.FullName FROM Contacts C1 WHERE C1.ID = ParentID ) AS ParentName,
  ChildID,
  (SELECT C2.FullName FROM Contacts C2 WHERE C2.ID = ChildID ) AS ChildName    -- Offending Clause
  FROM ContactRelationships
  WHERE ParentID = 1

The offending clause still returns NULL in the original form even if I run the query in a newly created session.

I have given up trying to use the sensitive query and I am using the query below with Delphi Lookup fields to find the Child information.

SELECT ID, ParentID, ChildID FROM ContactRelationships

It will have to remain a mystery to me.

Richard Harding

Richard


You're good to go on the Twilight Zone

Roy Lambert

Richard

> I tried creating a small application to demonstrate the above behaviour.
>
> * Created a new database with new application
> * Existing database with the new application
> * Existing database with existing application using a new form
>
> In all cases, the offending clause below that was returning NULL is now returning the correct result.
>
> SELECT
>    parentID,
>    (SELECT C1.FullName FROM Contacts C1 WHERE C1.ID = ParentID ) AS ParentName,
>    ChildID,
>    (SELECT C2.FullName FROM Contacts C2 WHERE C2.ID = ChildID ) AS ChildName    -- Offending Clause
>    FROM ContactRelationships
>    WHERE ParentID = 1
>
> The offending clause still returns NULL in the original form even if I run the query in a newly created session.
>
> I have given up trying to use the sensitive query and I am using the query below with Delphi Lookup fields to find the
Child information.
>
> SELECT ID, ParentID, ChildID FROM ContactRelationships
>
> It will have to remain a mystery to me.

I hate something like this remaining unsolved . I am happy to look at the pas/dfm of the offending form if you want.

John

Richard,

<< The offending clause still returns NULL in the original form even if I
run the query in a newly created session. >>

Hmm, did you check to see if maybe your existing project is picking up any
stray older EDB code/dcus from a project-specific compiler search path ?
That might account for the difference.

--
Tim Young
Elevate Software
www.elevatesoft.com

<<Hmm, did you check to see if maybe your existing project is picking up any stray older EDB code/dcus from a project-specific compiler search path ?
That might account for the difference.  >>

Yes . . . I am using EDB v 2.05.  I found a v2.03 package (edb203r2007run.bpl )in another in another directory.  Deleting this file seems to have fixed the problem.

Thank you.

Richard Harding . . .

<<I hate something like this remaining unsolved . I am happy to look at the pas/dfm of the offending form if you want.>>

Thank you for your offer but I think I have fixed the problem - (It was really Tim who fixed it)

Richard Harding