Search results

I'll put it this way, the MS Access query had some nulls there but when I did a check setting the same field to not null both queries match in the number of records. The original developer did not for some reason understand this. At over 500K records this may be why I saw all of those null...

Got it! For some reason Null values were affecting the Job Name field. Now it populates correctly! Access must only filter on non nulls in a left join. I added this and it works fine. WHERE dbo.T_Inspections.[Job Name] IS NOT NULL

Yes the linked tables are the same. Something with the Access query will pull the data that the SQL pass through cannot.

GPGeorge, I followed your instructions and have the same result.

No I don't see that as an issue. This query has left joins and the connection to the Receipts table is made in Access but I wonder if SQL cannot correctly make that join.

Yes just corrected that.

Correct! Empty Values in SSMS but not using MS Access SQL Query .

Yes the ODBC passthrough shows different data than the MS Access SQL which takes a long time. MS Access uses a linked table while the pass through goes straight to the tables. This is the MS Access query.

Here is my query: SELECT dbo.T_Inspections.Status, dbo.T_Inspections.Atts, dbo.T_Inspections.[Job Name], dbo.T_Inspections.Job_Id, dbo.T_Inspections.Est_Num_Completion, dbo.T_Inspections.[Street Addr], dbo.T_Inspections.City, dbo.T_Inspections.State, dbo.T_Inspections.County...