Arrgggg -- Suddenly, my combo box query stops working

[JimS]

I have a combo box on a form. Its row source is:

SELECT tblWorkOrders.ID, tblWorkOrders.WONbr, tblWorkOrders.HexNbr,
tblWorkOrders.Description, tblWorkOrders.ProjectID,
tblProjects.CapitalExpense, tblWorkOrders.WOExpiry
FROM tblProjects INNER JOIN tblWorkOrders ON tblProjects.ID =
tblWorkOrders.ProjectID
WHERE (((tblWorkOrders.HexNbr) Like [cbhex] & "*")
AND ((tblWorkOrders.WOExpiry) Is Null))
OR (((tblWorkOrders.HexNbr) Like [cbhex] & "*")
AND ((tblWorkOrders.WOExpiry)>=CDate([tbworkdate])))
ORDER BY tblWorkOrders.HexNbr;

[cbhex] is typically null.
[tbworkdate] is typically today, and at least a year prior to WOExpiry.

The rowsource has been working on a data entry form for months. I changed
the table slightly with respect to the "hex" field, but only to allow and
default to nulls. Today, after making those changes, the rowsource query
stopped working. I tried removing the entire WHERE clause, and it still
doesn't work. It pulls lots of rows, but not the most recent entries. Those
entries were likely made today.

It's a simple table and a pretty simple query. The project table contains a
record for the missing data, and I was able to pull all the records using a
simple similar query....

My only guess is the primary key, a long integer, has now exceeded 10,000. I
would expect the max to be much higher, but that's about the only thing I
see. Any other ideas? I'm stumped!

 

[JimS]

Figured it out. Null never matches anything...duh

 

[Jeff Boyce]

Jim

Any chance your computer was just upgraded to SP3 for Office 2003? There
are known issues with Access tables and comboboxes with this SP.

Regards

Jeff Boyce
Microsoft Office/Access MVP