[AccessD] NOT Query.

Hi Arthur,

I develop systems that handle business processes.  These can start one day
and end days or weeks later.  Users enter data as they have it, and some
fields are optional.  This kind of situation requires that fields be left
null, and I have to account for it.  

I do set up stage-gates.  A stage-gate is where a user can't move ahead
until certain data fields are populated or certain data conditions are met.
Any given business process may have from 3 to 8 stages.  Each stage is named
so users quickly know where the process is.

Hope this works as an example!
Dan



-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller
Sent: Tuesday, March 31, 2009 9:43 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] NOT Query.

This is a concept that was way beyond me, going back as far as it goes. Over
here we have the "never allow NULLs" camp. Over there we have the "Allow
empty fields" camp. I do not comprehend the purpose of the latter. Perhaps
some astute lister could educate me on this matter.

TIA,
Arthur
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com