Access invalid use of null error

It appears PrintImage1 is Null. Can you set a breakpoint and test? In reply to dhookom's post on January 10, You really need to provide additional information if you need prompt help. Where are PrintImage1 and PrintImage2 coming from? Are these text boxes on your form? Are there appropriate values in each? If PrintImage1 and PrintImage2 are controls or fields in the form's record source, it is advised to be more explicit with your code like: Me.

PrintImage1 Me. PrintImage2 Does your code compile? Works fine if I cut it down to only one image, but error out with 2 images. Again, does your code compile? Have you tried setting breakpoint and stepping through your code?

Lost, do not understand how to do either. That's because any equation that encounters a null value will always return Null. Although it's a nuisance, it makes sense. You can't evaluate an unknown value. If your data contains null values, use the Nz function to protect your expressions from this error. Specifically, Nz returns a value other than Null when it encounters Null as follows:. In this case, Nz returns 0 when Shipping equals Null. Use Nz in criteria and VBA expressions. Access projects don't support Nz.

In 3, you learned that Null doesn't equal anything. That's true, as long as you're using native functions and VBA. For instance, the following statement executed against an ADO Recordset object returns an error:. That's because ADO doesn't recognize the Is operator in this context.

The ADO library supports the Equals and Inequality operators when searching for or excluding null values. Fortunately, the correction is as simple as replacing the Is operator with the Equals operator:. You'll find Access a bit of an oddball on this issue.

Many libraries use the Equals and Inequality operators instead of Is. If a non-native library returns an error when working with null values, this switch will probably do the trick.

Not all aggregate functions consider null values. The good news is, there's a bit of reason to the inconsistency. An aggregate function that evaluates a field does not evaluate null values in its result. However, Count , First , and Last do evaluate null values.

It makes sense that they would--just because one field contains a null value doesn't negate the row's purpose within the context of the domain. If you want to exclude null values in a count, specify the field in the form Count field. The result of both forms may or may not be the same. The point is, the field-specific form won't consider null values in its count.

Otherwise, Jet excludes the row from the results. This behavior is inherent in the equality issue discussed in 3. Because Null doesn't equal anything, it can't satisfy a condition other than Is Null.

For instance, the simple expression. Now, that might be what you want, but it might not. If you want to include null values, include Is Null in the condition as follows:. May ask end up with a different solution. Which would indicate that you have at least one entry where there is no value for a DepartDate. If that's the case then you'll need to use IsNull to test before continuing our Nz to assign a default value of the is a null entry.

As for the blank record at the bottom of the continuous form, there is no issue. It does not get looped through an. Bookmark With rs. MoveFirst Do While Not. Update End If. If Me. Bookmark End If With Me. OpenRecordset End With. With rsFiltered. Hi Daniel, I take your point about mysetup and code being different, despite the error message being the same. With that in mind, I have started a new post here:. And I have posted your most recent suggestion to my problem there also.

I will test both suggestions and come back to you, on the other post. Well, Microsoft has just screwed up this forum royally, so presently I can view the webpage you provided a link to. If I were to use your code for the arrive button too, would it be a simple case of swapping around the 'Arrives' with the 'Departs' or am I liable to release a can of worms?

I will have to come back to you later Daniel, I am in the UK and it's late here now, and I have been starting at the screen for too long Hi Dnaiel, I have has a chance to test both code functions, and neither of them were successful. The strange thing is that I watch the code cascade through the rows and realised that it somehow was managing to pick up the number of days within [ StayDurationDays] and add that number to [ArriveDate].

I post the form's query below which may provide a clue as to how or why your code behaves in this way. Jeremiah Ochepo. Hello Everyone, Please I need help.