| Member with 2 posts. THREAD STARTER | | Join Date: Mar 2012 Experience: Beginner | |
OBP - first off, glad I got your attention, and Thanks for the quick reply. You seem to be 'the man' when it comes to talking normal people through complicated DB issues. I was reading some of your prior posts this weekend to try to get my db off the ground... Also, I am perfectly fine with using Access 2003, it's just that I only have 2007 installed on my computer... But, I would assume that you can save a backwards compatible DB in 2003 form, akin to what Excel can do.
a) Almost always, the personnel are going to be the same. In actuality, what will happen is there will be about 20 people whom the tasks can be assigned to. Of those 20, there is a subset of only 3 people who will be assigning tasks. However, the assigners can assign stuff to themselves. So, the lists won't techinically be exactly the same, but I see no issues in using the same list for both references. However, there are some rotating contractors involved, so that ability to add or remove people to this list will be critical.
b) I don't see any reason why Tasks would NOT be able to be in a table (is there any specific reason why it physically would not be able to go in a table?), for both the short and long text. I actually had initally tried to talk them into doing the entire thing in Excel tables, but the big thing they want is the 'program' to be able to view all open inquiries and add text to them 'on the fly' while reviewing. This whole thing is SOLELY for viewing open inquiries in the review meetings and being able to add notes which will 'attach' to the inquiries. Also, there may not be a limit to the notes. It is very possible that an inquiry is issued but does not get addressed for several years, so I need the ability to add (possibly) a few hundred notes (If one ends up being a very large project, they will add the note "No Change" or something to that effect each week until the inquiry is closed, and they currently have inquiries over 2 years old, so that's 104+ notes).
c) Yes, the idea was for them to be hand-typed in. The hand-written sheets come from a variety of places to one of the 3 people I mentioned in (A), and then the core group of 20 guys will interface with this database just to see the status of the inquiries and see what has been assigned to them, and also to see any notes that were added during the review meetings. Each of the inquiries will likely develop into a much larger task. I think I see where you're going with this (elminiating the need for hand-written paper), and the real issue with it is that there are people who will be submitting these "inquiries" who do not always have a computer to interface with. So, I don't see any way around the hand-written part. although I am open to suggestions.
You're first sentence is very encouraging. That is what I've been telling myself this entire time, that despite the fact I am database rusty, this seems like just about the easiest database that one could ask for. I was speaking of starting from scratch because I have been, thus far, very unsuccessful at maniuplating a template into something that I want. The template designs seem to me to be very rigid. But, as I said before, I am rusty on the software, and very open to suggestions. I also have only really looked at Microsoft templates, not any from 3rd parties, if you have some template suggestions. Although, as I said, I have not been extremely successful in manipulating tempates to my needs.
Thanks again. |