By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
444,155 Members | 2,518 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 444,155 IT Pros & Developers. It's quick & easy.

#Error Issue

P: n/a
I have a situation with a query that is formed by linking a whole lot of 2
column 'sub' queries to a 'main' query using left joins. The main query is
a list of ID's and the sub queries all contain a specific piece of
information related to each id. So by linking them all together I can get
the full picture by ID -in theory. The problem I have is that where there
is no matching record in a sub query, I am getting a '#Error' returned where
I would expect a Null. This #Error is terminal in that any subsequent
evaluation on this data also returns #Error - including ISError(). I cant
figure out a way to make the #Error go away, especially since it doesnt
appear in the sub queries themselves so I have tracked it to the source. (I
dont get the error if I change the left joins to inner joins but this
destroys the logic of the query and is not viable.)

Suggestions or advice from those who genuinely understand why I am getting
this #Error would be gratefully received.

Andrew C
Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
RE/
Suggestions or advice from those who genuinely understand why I am getting
this #Error would be gratefully received.


How about pasting the SQL into a followup message?
--
PeteCresswell
Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.