#1  
Old 29th January 2007, 10:54 PM
Ken Randall
 
Posts: n/a
Default Unable to Resolve Identifier "O"."ProspRef"

Please be aware that I still get an error when running the following query
with today's nxServer snapshot.

Ken

select O.HouseRef,O.ProspRef,O.BridgingFacilities,O.Incom pleteChain,
O.AnticipatedCompDate,O.FinanceCo,O.FinanceAmount, O.FinanceContact,

O.FinanceConfirmed,O.AnticipatedExchDate,H.Address String,

substring(O.HouseRef from 1 for 3) Branch,

(SELECT NameAndAddressString from

(SELECT OrigBranchRef, NameAndAddressString from EstatePro.Prospects

where OrigBranchRef=O.ProspRef

UNION

SELECT OrigBranchRef, NameAndAddressString from Archive.Prospects

where OrigBranchRef=O.ProspRef

) yyy

) NameAndAddressString

from Offers O

left join Houses H on H.HouseRef=O.HouseRef

where H.SaleStatusInt in (1,7,4,10)

order by AddressString,NameAndAddressString


  #2  
Old 30th January 2007, 12:07 AM
Eivind Bakkestuen [NDD]
 
Posts: n/a
Default Re: Unable to Resolve Identifier "O"."ProspRef"

> Please be aware that I still get an error when running the following
> query with today's nxServer snapshot.


Please be aware that the point of publishing the fix list is so YOU can
check if the issue number is SUPPOSED to be fixed. Also be aware what the
fix list page says about waiting.

It should be obvious that if the fix isnt listed as having been verified and
closed, there's not much point in testing for it (and certainly not in
telling us its not done yet; we already know that .

--

Eivind Bakkestuen
Nexus Database Systems Pty Ltd


  #3  
Old 30th January 2007, 01:43 AM
Ken Randall
 
Posts: n/a
Default Re: Unable to Resolve Identifier "O"."ProspRef"

"Eivind Bakkestuen [NDD]" <Ieivind.bakkestuenHATE@nexusdb.comSPAM> wrote in
message news:45be01c4@wic040d....
>> Please be aware that I still get an error when running the following
>> query with today's nxServer snapshot.

>
> Please be aware that the point of publishing the fix list is so YOU can
> check if the issue number is SUPPOSED to be fixed. Also be aware what the
> fix list page says about waiting.
>
> It should be obvious that if the fix isnt listed as having been verified
> and closed, there's not much point in testing for it (and certainly not in
> telling us its not done yet; we already know that .
>
> --
>
> Eivind Bakkestuen
> Nexus Database Systems Pty Ltd
>

I thought it was mentioned in the fix list!

Ken


  #4  
Old 30th January 2007, 02:17 AM
Brian Evans [NDX]
 
Posts: n/a
Default Re: Unable to Resolve Identifier "O"."ProspRef"

Ken Randall wrote:
> Please be aware that I still get an error when running the following query
> with today's nxServer snapshot.
>
> Ken
>
> select O.HouseRef,O.ProspRef,O.BridgingFacilities,O.Incom pleteChain,
> O.AnticipatedCompDate,O.FinanceCo,O.FinanceAmount, O.FinanceContact,
> O.FinanceConfirmed,O.AnticipatedExchDate,H.Address String,
> substring(O.HouseRef from 1 for 3) Branch,
> (SELECT NameAndAddressString from
> (SELECT OrigBranchRef, NameAndAddressString from EstatePro.Prospects
> where OrigBranchRef=O.ProspRef
> UNION
> SELECT OrigBranchRef, NameAndAddressString from Archive.Prospects
> where OrigBranchRef=O.ProspRef
> ) yyy
> ) NameAndAddressString
> from Offers O
> left join Houses H on H.HouseRef=O.HouseRef
> where H.SaleStatusInt in (1,7,4,10)
> order by AddressString,NameAndAddressString


Can use COALESCE to pick the first sub query that returns a
NameAndAddressString.

SELECT O.HouseRef,O.ProspRef,O.BridgingFacilities,O.Incom pleteChain,
O.AnticipatedCompDate,O.FinanceCo,O.FinanceAmount, O.FinanceContact,
O.FinanceConfirmed,O.AnticipatedExchDate,H.Address String,
substring(O.HouseRef from 1 for 3) Branch,
COALESCE((SELECT NameAndAddressString
from EstatePro.Prospects
where OrigBranchRef=O.ProspRef),
(SELECT NameAndAddressString
from Archive.Prospects
where OrigBranchRef=O.ProspRef))
as NameAndAddressString
FROM Offers O
LEFT JOIN Houses H ON H.HouseRef=O.HouseRef
WHERE H.SaleStatusInt IN (1,7,4,10)
ORDER BY AddressString,NameAndAddressString;

--
Brian Evans [NDX]
Ottawa, ON, CANADA
GMT-5
  #5  
Old 30th January 2007, 02:56 AM
Ken Randall
 
Posts: n/a
Default Re: Unable to Resolve Identifier "O"."ProspRef"

"Brian Evans [NDX]" <bevanson@rogers.com> wrote in message
news:45be2000$1@wic040d....
> Ken Randall wrote:
>> Please be aware that I still get an error when running the following
>> query with today's nxServer snapshot.
>>
>> Ken
>>
>> select O.HouseRef,O.ProspRef,O.BridgingFacilities,O.Incom pleteChain,
>> O.AnticipatedCompDate,O.FinanceCo,O.FinanceAmount, O.FinanceContact,
>> O.FinanceConfirmed,O.AnticipatedExchDate,H.Address String,
>> substring(O.HouseRef from 1 for 3) Branch,
>> (SELECT NameAndAddressString from
>> (SELECT OrigBranchRef, NameAndAddressString from EstatePro.Prospects
>> where OrigBranchRef=O.ProspRef
>> UNION
>> SELECT OrigBranchRef, NameAndAddressString from Archive.Prospects
>> where OrigBranchRef=O.ProspRef
>> ) yyy
>> ) NameAndAddressString
>> from Offers O
>> left join Houses H on H.HouseRef=O.HouseRef
>> where H.SaleStatusInt in (1,7,4,10)
>> order by AddressString,NameAndAddressString

>
> Can use COALESCE to pick the first sub query that returns a
> NameAndAddressString.
>
> SELECT O.HouseRef,O.ProspRef,O.BridgingFacilities,O.Incom pleteChain,
> O.AnticipatedCompDate,O.FinanceCo,O.FinanceAmount, O.FinanceContact,
> O.FinanceConfirmed,O.AnticipatedExchDate,H.Address String,
> substring(O.HouseRef from 1 for 3) Branch,
> COALESCE((SELECT NameAndAddressString
> from EstatePro.Prospects
> where OrigBranchRef=O.ProspRef),
> (SELECT NameAndAddressString
> from Archive.Prospects
> where OrigBranchRef=O.ProspRef))
> as NameAndAddressString
> FROM Offers O
> LEFT JOIN Houses H ON H.HouseRef=O.HouseRef
> WHERE H.SaleStatusInt IN (1,7,4,10)
> ORDER BY AddressString,NameAndAddressString;
>
> --
> Brian Evans [NDX]
> Ottawa, ON, CANADA
> GMT-5


Brian,

You're a star - works perfectly. Many thanks.

Ken




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
2.0.599r3: Query that should work returns Unable to resolve the identifier"#t1"."ContratoId" =?ISO-8859-1?Q?=22Rodrigo_G=F3mez_=5BNDX=5D=22?= nexusdb.public.support.sql 2 4th November 2006 10:03 AM
On the "empty identifier" front ... Martijn Tonies nexusdb.public.support.sql 3 7th September 2006 07:54 PM
SQL "TOP" & "GROUP" question fred nexusdb.public.support.sql 38 10th August 2006 05:49 PM
SQL query to search on a field that is "similar to a set" or "mask"? J Tabor nexusdb.public.support.sql 2 10th May 2006 02:20 PM
Announcment! "The Keep" ver 2.0.0.1 and "Po Boy Application LifeCycle Management Utility" ver 1.0.0.l are now both available for free download! Robert Meek nexusdb.public.support.thirdparty 1 11th July 2004 10:23 AM


All times are GMT +11. The time now is 12:24 AM.


Powered by vBulletin® Version 3.6.8
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.