Icon View Incident Report

Serious Serious
Reported By: Uli Becker
Reported On: 7/20/2009
For: Version 2.02 Build 15
# 3044 Specifying a Database Correlation Name in a DML Statement Can Cause #401 Error for Other Tables

got an error "The table or view Anforderungen does not exist..." when preparing the following query:

Of course the table exists. The query wasn't changed and still works in Build14 which I reinstalled. The problem seems to be the join of different databases.

The database from which I am executing the query is named "Labor". Changing the query to:

join Labor.Anforderungen a...


select distinct PatientenID, Name,Vorname,GebDat,Anrede,Strasse,PLZ,Ort from informa.Patienten p
join Anforderungen a
on a.PatientenID = p.patientenID join informa.Scheine s on
a.ScheineID = s.ScheineID
where  not (coalesce(PLZ,'') = '''' or coalesce(Strasse,'') = '' or
 coalesce(Ort,'') = '') and (abgerechnet = false and
Ambulant = :true and Gruppe <> 'IM1')
and (s.privat = true)
order by Name, Vorname

Resolution Resolution
Fixed Problem on 7/23/2009 in version 2.03 build 1

Products Affected Products Affected
ElevateDB Additional Software and Utilities
ElevateDB DAC Client-Server
ElevateDB DAC Client-Server with Source
ElevateDB DAC Standard
ElevateDB DAC Standard with Source
ElevateDB DAC Trial
ElevateDB LCL Standard with Source
ElevateDB VCL Client-Server
ElevateDB VCL Client-Server with Source
ElevateDB VCL Standard
ElevateDB VCL Standard with Source
ElevateDB VCL Trial