Finding the most current row where it the row meets all multiple conditions

Question

Need to find the latest barcode to check if it is expired previous to today.  Currently getting barcode that has expired but that happened after the stateID changed to 2 not earlier when the stateID  is 1 and it needs to be
the current record by date.  The expired is done by a scalar function that uses the barcode that calculates an expired container. The expired container from the cte  is either 1 for expired or 0 for non expired containers
from the containerHistory table
stateID    barCode           dateEntered
1             901178-2240   2014-11-15 10:34:09.693
2             901178-2240   2014-11-19 22:07:45.0230
From the cte table
stateID    dateEntered                       barcode            containerExpired        
1            2014-11-19 22:07:45.000   901178-2240              1
From the global ##Temp table
2              2014-11-19 22:07:45.000  901178-2240 
;with cte AS(
SELECT stateID, barcode, dateEntered, containerExpired
FROM barcode.dbo.ContainerHistory
WHERE dateEntered >= DATEADD(DAY, DATEDIFF(DAY, 0, CURRENT_TIMESTAMP) -7, 0)
AND dateEntered < DATEADD(DAY, DATEDIFF(DAY, 0, CURRENT_TIMESTAMP), 0)
AND stateID = 1 AND containerExpired = 1
SELECT stateID, barcode, dateEntered, containerExpired
INTO ##Temp
FROM
(SELECT barcode, stateID, dateEntered, containerExpired, row_number() over(partition by barcode, containerExpired order by dateEntered) seq
FROM cte
WHERE dateEntered <= (select max(dateEntered) from cte where containerExpired = 1 AND stateID = 1) AND containerExpired = 1
) d
WHERE seq = 1 ORDER BY dateEntered
SELECT * FROM ##Temp ORDER BY barcode
SELECT barcode, stateID, dateEntered WHERE containerID IN (SELECT barCode AS containerID FROM ##Temp) ORDER BY containerID, dateEntered
DROP TABLE ##Temp

Answer 1

Youir approach is wrong. To track the history of, say, Foobars we need to see time as a continuum and model it as (begin_date, end_date) pairs that define when a foobar had a particular value. Here is the skeleton. 
CREATE TABLE Foobar_History 
(foo_id CHAR(9) NOT NULL, 
 start_date DATE NOT NULL, 
 end_date DATE, --null means current 
 CHECK (start_date <= end_date),
 foo_status INTEGER NOT NULL, 
 PRIMARY KEY (foo_id, start_date)); 
When the end_date is NULL, that state of being is still current. You use a simple query for the status on any particular date;
SELECT * 
  FROM Foobar
 WHERE @in_cal_date
     BETWEEN start_date
      AND COALESCE (end_date, CURRENT_TIMESTAMP);
There are more tricks in the DDL to prevent gaps, etc
CREATE TABLE Events
(event_id CHAR(10) NOT NULL,
 previous_event_end_date DATE NOT NULL  
 CONSTRAINT Chained_Dates  
  REFERENCES Events (event_end_date), 
 event_start_date DATE NOT NULL, 
 event_end_date DATE UNIQUE, -- null means event in progress
  PRIMARY KEY (event_id, event_start_date), 
 CONSTRAINT Event_Order_Valid 
  CHECK (event_start_date <= event_end_date), 
 CONSTRAINT Chained_Dates 
  CHECK (DATEADD(DAY, 1, previous_event_end_date) = event_start_date)
-- CHECK (previous_event_end_date + INTERVAL '01' DAYS) = event_start_date)
-- disable the Chained_Dates constraint
ALTER TABLE Events NOCHECK CONSTRAINT Chained_Dates;
GO
-- insert a starter row
INSERT INTO Events(event_id, previous_event_end_date, event_start_date, event_end_date)
VALUES ('Foo Fest', '2010-01-01', '2010-01-02', '2010-01-05');
GO
-- enable the constraint in the table
ALTER TABLE Events CHECK CONSTRAINT Chained_Dates;
GO
-- this works
INSERT INTO Events(event_id, previous_event_end_date, event_start_date, event_end_date)
VALUES ('Glob Week', '2010-01-05', '2010-01-06', '2010-01-10');
-- this fails
INSERT INTO Events(event_id, previous_event_end_date, event_start_date, event_end_date)
VALUES ('Snoob', '2010-01-09', '2010-01-11', '2010-01-15'); 
--CELKO-- Books in Celko Series for Morgan-Kaufmann Publishing: Analytics and OLAP in SQL / Data and Databases: Concepts in Practice Data / Measurements and Standards in SQL SQL for Smarties / SQL Programming Style / SQL Puzzles and Answers / Thinking
in Sets / Trees and Hierarchies in SQL