I have not got a solution, if you downloaded all I have in the db, the queries and the forms is all I have.
It works now by just selecting Y/N, and it monitors which date it is. You can select all the categories at once or one of them. It works but wont allow me to make a report that totals the calls by category by month and reports it in the report.
I thought making a button to be the easiest to have for the users, could be multiple users, so it may not be possible, but I still need the report if not the buttons
ok, i've had another look at your database. i'm afraid i can't help. either:
it's such a mess i have no idea how you are currently going to add any useful features or user-friendly interface
or
it's waaaaay to advanced for my expertise.
i personally think it's the former - you have a lot of work to do on that database my friend. i suggest you rethink your approach. these are a few of the reasons i think you will constantly have trouble try to make your current setup working:
for starters, you tables look de-normalised and nomenclature all over the place (tables are conventionally prefixed with "tbl", forms with "frm", queries with "qry", etc) - why don't you use your PhoneCategory table in your form using a multiselect listbox or a subform, instead of using checkboxes? that way, if any new categories are added, you don't have to re-code anything in the form/module, it's just "there" for the users.
your combobox for Users uses a value lists - you should instead have a table tblUsers and use that (or a query of the table - makes it more flexible, e.g., you can filter out ex-employees) as the combo's row source.
you have the same code repeated in several places rather than just referring to it from one place
you're best off using Now() or Date() as the default value for CallDate - then the user can put their phonecall in 'real-time' without having to remember what the date is or remember to change it everyday, or accidentally putting in the wrong date or with the wrong format.
so as you can see, there's lots of ways to improve your design. start off by reading about normalisation. to start you off, i would suggest at least these tables:
tblCalls
-------------
CallID (PK, Autonumber)
CallDate
UserID (FK, Number) - see tlkpUsers
tblCallDetails
-------------
DetailsID (PK, Autonumber)
CallID (FK, Nnmber)
CategoryID (FK, Number)
tlkpUsers
-------------
UserID (PK, Autonumber)
UserCode (Text)
UserName (Text)
tlkpPhoneCategory
-------------
CategoryID (PK, autonumber)
Category (Text)
search the forum for other people creating telecommunications databases (there have been HEAPS), and here's some detailed descriptions of normalisation, but you should do a lot of your own reading in addition to these:
http://www.access-programmers.co.uk/forums/showpost.php?p=839040&postcount=13
http://www.access-programmers.co.uk/forums/showthread.php?p=913461#post913461
i know it's a lot of work, but believe me - as someone who also started with really bad database design - it's worth it in the long run (and short run, as it happens).