BobTheMasher
Of what, we don't want to know.y
Posts: 4,243
I have basic experience making databases, I used one to keep track of ad sales for the newspaper back in high school. Nothing fancy, obviously, but I get the general idea.
What I'm trying to do (well, me and my roommate/coworker) is to create a simple dispatch database for our office, a parking enforcement operation. Essentially, we need a table of calls to track activity, and a table of officers to track each officer's status.
Each call would include a unique call id, the dispatcher who took the call, the date and time of the call, the reporting party and contact information, and the location and details of the call.
Each officer would have a status (busy, off duty, on break, etc.) and an assignment (mobile, on foot, special assignment, etc.)
Creating this is pretty simple, we've got the basic structure set up and functional. The only things I am trying to figure out are convenience and ease-of-use things, like having the two tables interact with each other to make sure statuses sync up, and automating date/time updates, outputting reports to a separate file (for supervisors to access) and things like that.
I think I've gotten most of it worked out, you're right, the microsoft help files for access are actually quite helpful. I also have limited programming experience, including using vb in excel a year or two ago for a class. It's just finding where to start for some of this stuff that's tough, haha.