Access date is null

In my query, "Date Closed" field criteria "is null". Any suggestions? Follow Post Reply. JKing 1, Expert 1GB. Could you post your SQL for this query? This helps greatly in solving problems. Sex, tblNameAge. Married, tblNameAge. Divorced, tblNameAge. Yes, that's what I'm looking for but post the SQL for the query you're having a problem with. The one you spoke of in your first post.

WebDueDate, [Job Log]. ThePulse, [Job Log]. Internet, [Job Log]. Desktop, [Job Log]. MedWeb, [Job Log]. WebDueDate; Thanks! Local time Today, Joined Aug 29, Messages 8, Try; Code: Copy to clipboard. John Big Booty, That did the trick!

Anyway, thanks for the help!! Can anyone recommend a really good access vba book? Brianwarnock Retired. Local time Today, Joined Jun 2, Messages 12, Local time Today, Joined Sep 12, Messages 14, You must log in or register to reply here.

Similar threads C. Replies 26 Views Jan 4, Chief. Solved Enter a date, check box is true, click checkbox to false, clear date. Replies 7 Views Nov 3, Chief. Solved Date Entry in access not picked by Search Form.

I'm getting data type mismatch error - since it's a date field in Access. Thanks - can't do it. I have multiple fields as a date fields - for example Termination date. It will mean to everybody else that the person is termed when it's not.

For example - some reports are triggered by this field - if it has a value. So I do need to have either valid date in the field or have Null value in it and need ability to clear date field - if someone entered date by mistake. To som e degree I agree with Swade's logic in this.

If you cannot place a null value in an Access datetime field at least if you want to use a. NET interface then you may have to change the logic that allows that field be the determinant for whether or not a person has been terminated. At least in the user interface you could display a blank when necessary so the user doesn't have to be confused.

I have 8 date fields total that would need those changes - if I decide to go this way. As I mentioned before - some of those fields will trigger updating some other tables - if there are values in those fields. I'm not sure that I'd want to re-write the processing because of it. It'd probably be more efficient just to switch all date fields to strings in the table in Access and I won't have Null problem anymore but will have to re-do Crystal reports that use date fields.

I thought that there must be an alternative way of doing it. You did mention ADO reference and using recordset functionality - can you explain it a little more? Will it solve Null - Date problem? Are there any examples on the web? I believe it'll be again the problem with VB not accepting Null value. I'm guessing that if nobody else experienced this problem or have not found an answer - I'll have to switch to string field. Ask a question.