Re: Problem adding "<16" into DCOUNT function to reflect a cap of 16???

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



tables are: tblCUSTOMER INFO and tblEVENTS with a one to many relationship
by CustID field.

forms are: frmCUSTOMER INFO and frmEVENTS
in the frmEVENTS, a user uses a combo box with custID to pull up the CustID
and CustName. the subform reflects tblEVENTS in datasheet view where the
user can schedule the customer for a testing date. the user would go into
frmEVENTS, pull up the customer throught combo box and schedule them for a
test session in the subform.

tblEVENTS
Event(a drop down menu with 8 different tests that customer can take)
EventDate(current date default)
EventTime(am or pm)
ScheduledBy

at the top of all this shows:

Date() Date()+1...
am-session (dcount)
pm-session (dcount)
where the dcount function calculated the number of customers who has been
scheduled for a am/pm session on a certain date. this shows that this many
customers has been reserved for this session on this date. this number
needs to be less than or equal to 16.

your suggestion about not being able to choose or flag closed suggestions
is great. hope this helps...

--
Message posted via http://www.accessmonster.com
.



Relevant Pages

  • Re: Problem adding "<16" into DCOUNT function to reflect a cap of 16???
    ... tblCUSTOMER INFO and tblEVENTS with a one to many ... > relationship by CustID field. ... > in the frmEVENTS, a user uses a combo box with custID to pull up the ... > view where the user can schedule the customer for a testing date. ...
    (microsoft.public.access.forms)
  • Re: Access the right program for the job?
    ... include any other fields that describe a customer only; ... as the primary key, and get rid of the PartID field. ... CustID (foreign key from tblCustomers) ...
    (comp.databases.ms-access)
  • Re: Add Records
    ... One containing each customer, just once. ... The other table would have (apart from its own Primary Key) a number field ... Because the subform and mainform are linked, when you are on a customer's ... CustID (this is a number field. ...
    (microsoft.public.access.tablesdbdesign)
  • Re: Add Records
    ... One containing each customer, just once. ... The other table would have (apart from its own Primary Key) a number field ... Because the subform and mainform are linked, when you are on a customer's ... CustID (this is a number field. ...
    (microsoft.public.access.tablesdbdesign)
  • Re: Access the right program for the job?
    ... include any other fields that describe a customer only; ... as the primary key, and get rid of the PartID field. ... CustID (foreign key from tblCustomers) ...
    (comp.databases.ms-access)