Forum Home
Press F1
Thread ID: 98094	2009-03-11 03:58:00	MS Access query question	Tony (4941)	Press F1

Post ID	Timestamp	Content	User
755441	2009-03-14 04:49:00	Yeah, I've found Access to be a real pain at times when Null or Empty values get into queries. What seems to work perfectly turns to crud when a field has nulls. Another strategy I've resorted to in the past is to run action queries beforehand to replace all Null and Empty values in a table with Zero, or some other value that I use to represent 'not used' within the database. Another change to your table design to set default values of Zero (not null), or Date() for date values, and to include a validation rule of IsNotNull may be another way to avoid issues like this. I seem to recall some inconsistent use of syntax between gueries and macros at times too, like one using IsNotNull, and another using Not(IsNull(...)) Access is a really great piece of work, but it has some quirky little traps that can eat up days of design and debugging.	Paul.Cov (425)
1 2