Re: oledb correlated subquery error
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Wed, 23 May 2007 22:25:52 +0000 (UTC)
(musicgal501@xxxxxxxxxxx) writes:
Thank you very much for replying so promptly! The reason for the
subquery for the 'payTax1OnConsign' field was the fact that the join
is conditional and access will not allow a right(outer) join in this
circumstance. The most strange thing is that for the invoice where the
query fails, there is only one line on the invoice, and only one line
is returned by your query (and mine when I run it in Access). Have you
heard of this before?
Let me it put it this way: I have heard of cases before where people
have been dead sure that it is a way which it isn't. I may have committed
that sin myself, once or thrice.
Without having a script that populates the table and reproduces the
error (if there is any), I cannot really comment. On top of that, Access
is not in my realm, I'm an SQL Server guy.
I guess there could be some kind of corruption, but you are probably
better off asking in an Access newsgroup about that.
--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.
- References:
- Re: oledb correlated subquery error
- From: musicgal501
- Re: oledb correlated subquery error
- Prev by Date: Re: OLE DB Property Sets and Property Groups
- Next by Date: How to determine if the Access Connectivity Engine (ACE) is installed?
- Previous by thread: Re: oledb correlated subquery error
- Next by thread: How to determine if the Access Connectivity Engine (ACE) is installed?
- Index(es):
Relevant Pages
|
|
