I have a DB thats working fine, but (there always is a but) I now need to do something a little bit different. I need to be able to track my originators and who they have brought into the company. So I will have an originator and many down-line originators, and these people that come in down-line will have people coming in down-line from them and so forth and so on. I have a table that has all originator info and originatorID, but will I need another table or can I just add to the exisisting one. Here is the table structure:
Originators:
-------------
OriginatorID -autoNumber
FirstName - Text
LastName- Text
OrigSSN- Text
Address- Text
City- Text
State- Text
PostalCode- Text
HomePhone- Text
WorkPhone- Text
CellPhone- Text
FaxPhone- Text
EmailName- Text
BirthDate- Date/time
Level- Text
If more info is needed please let me Know.. Thanks in advance.
I am trying to deconstruct a database that has several linked tables. Is there a way to find the source database for the linked table from within the original database?
I work in a lab and am looking to track data associated with samples on PCR plates usually in 2 formats
96 well (8x12) rows A-H and Columns 1-12 384 well (16-24) row A-P and Columns 1-24
each well will have at least 3 pieces of information associated with it:Sample Assay Qulaity Score
but more may be added as I progress with the design.
field such as run name run date and operator for each plate would also be needed
What would be the best way to structure the table?
Obviously listing well A1, sample in A1, QA for A1 etc etc as fields wouldn't work as theres a 255 field limit and 3*96 = 288 and thats before we even get to 384
I could have a table for each run but that feels like bad design to me, as if you wanted to look at quality trends across time you would need to query multiple tables and query the date associated with each to even knwo which table to look in
A table for each well along with its QA score, assay and a look up field linking it to a list of plates, which would contain the run date etc. (this table listing runs is already present in my database)
Some background on current structure
Tables
Booking - contains a list of worksheet numbers along with info such as submitter, and conditions for the test such as assay
Experiment - expirment number conditions and associated DNAs
DNA - a list of dna samples
Plate - name of plate and info such as run date and associated worksheets
I am looking to track the salary information for my small firm over a number of years. Does it make sense to create a table with multiple fields that would be structured like this (2011401(k), 2011Medical, 2011 LifeInsurance, 2012401(k), 2012Medical, 2012LifeInsurance, etc) or is there a better way to tackle this?
Im trying to create a database to track who worked on what item and on what date, with four tasks required to complete the item.To give an example:I have a factory that builds Lego models, for each model there are four steps:
1)Unbox Parts 2)Sort Parts 3)Build 4)Check build
Any employee can work on any task, and multiple tasks can be done by the same employee.Having a completed item table with a field for each task, and a date for each task, with one to many relationships from employee id to each task type. This failed as I needed many to many, so I made a junction table to link them, and this is where I get a little muddled.
Do I need a table of task types, then a table tracking each task to feed into the item table, or is there a simple solution I'm overlooking?
I am developing a claim tracking database that tracks dates of events that occur in the course of processing a claim; such as, Loss Date, Report Date, Estimate Date, Payment Date, etc.
With this table structure there is a many-to-many relationship between Claims and Events, but, there will only be one of each event per claim. Is there a better way to set up the tables to enforce a 1-to-1 relationship?
I was planning on creating a form for the Claim table with a subform for the Events joined on ClaimID and fkClaimID, but that would allow users to create more than one set of Events per claim, if that makes sense.
I'm creating an attendance tracking system, the attendance system needs to : Allow an instructor to enroll students into one or more classes, and then add attendance by date to each class(es). The problem that I'm having is, attendance is tracked by the number of hours that a student attends class. For instance, if class1 is in session from 8a.m. - 12p.m. student1 may only stay 2.50 hours of that class and student2 may stay 3 hours. The teacher needs to be able to add attendance to class1 for July 12, 2013 and add hours for each student enrolled in this class session who attended on that day. I have the following so far, minus the attendance:
Students -This is just the basic demographic information that instructors will need to enter on students. StudentID (PK) StudentLastName StudentFirstName DateOfEnrollment LevelOfStudy DateOfBirth
Location - These are the locations in which our students can attend classes LocationID (PK) LocationName County City LocationPhoneNumber LocationFaxNumber
Classes - These are the classes that our students can attend. CRNNo (PK) ClassName LocationID InstructorID
Instructor - These are the instructors that teach our classes. InstructorID (PK) InstructorLastName InstructorFirstName InstructorEmailAddress
Enrollment - This table enrolls the student into a class StudentID(PK) CRNNo (PK) LocationID (PK)
I have a DB I'm using to track training for assigned people. Right now the training gets put in the DB at the end of the day by going through each persons record and adding the training that they did for the day. As you can see when training 30+ people a day, putting this in the system can take awhile. I'm trying to find a way to do a mass input to cut down time and could use some help with this.
What I like to do at the end of the is select the ClassID/DateTaken items once and then type in a just the 30+ list of employeeID's click a button and append it to the my 3rd table. Of course writing it out like this makes me think it should be easy but for some reason I'm lost. Does anybody have any suggestions?
I need help finding an existing or making a db. This db does not have much to it, so I am getting frustrated finding/making one.
My company has equipment that is stored in one of three places, customers, trucks of employees, and other(like warehouse, or out for repair). The db should be able to give me a report of where everything is on a given day, and a report of what was in a given customers property during the job(this is not for a single day, but for the duration of the job).
If someone knows of an existing db like this, I would appreciate a link. If you want to help, it is appreciated. At this point I would not mind paying someone to do this for me, as long as it wont cost too much.
Hi,I'm looking for a bug/issue tracking solution done entirely in MS Access. Does such a thing exist?My requirements are that it must need only Access, and be accessible in a shared environment solely by opening a .mdb file from a shared folder. It must support various issue lifecycle related things, and the stuff those tracking systems do in general.It may or may not be commercial software.If anyone knows of such an available solution, please let me know.(And yes, I've searched on Google, and haven't found anything worthwile, so that's why I'm asking here now.)thx
Is there a way to track changes made by different users to access tables? For instance if several users update or change data in various records is there a way to track when and what was changed (before and after data)?
I have read all of the audit trail stuff and searched on my subject but I think my solution could be simpler,
All I want to do is copy the values of the current record on my form into a history table with all the same fields.
Example Form: [ID], [Machine], [Task], [Task Due], [Task Complete] I want to put a button on the form that reads complete task and when the user pushes the button it copies all of the details for that specific record they are looking at into my History Table that contains all of the same fields.
This will give me basic history on when each task was completed for a machine and I can access for reporting
I consider myself an intermediate ACCESS user and can get around it with little trouble with the help of the internet and the help file.
I am trying to design a database that is fairly simple in design, it is for tracking the status of documents at our work center. Basically we have personnel reports that are passed around the different people and different dates.
I have a main form that has the info on the person along with dates that it is due.
Then a sub form that has the date sent and where it went to.
My problem lies in that I want to keep track of the whole history of the document but when i print out a report or export the data to excel to put up in powerpoint I need to have just the most recent date sent only item.
I have 2 tables one with user info and another with the routing info with its own primary key along with a identifier key to link the primary and sub form.
Of course it is easy to create a report with the data to show all the different routing steps but not just the one with the most recent date.
I'm looking for a bug/issue tracking solution done entirely in MS Access. Does such a thing exist?
My requirements are that it must need only Access, and be accessible in a shared environment solely by opening a .mdb file from a shared folder. It must support various issue lifecycle related things, and the stuff those tracking systems do in general.
It may or may not be commercial software.
If anyone knows of such an available solution, please let me know.
(And yes, I've searched on Google, and haven't found anything worthwile, so that's why I'm asking here now.)
I'm trying to set up a database to track a huge group of corporations. There is the parent company, then a bunch of subsidiaries below it. Some subsidiaries have another layer of multiple subsidiaries below it, some have none. Any thoughts as to how to do it???
I am tracking training for employees. I have a database that keeps track of the dates a particular training was taken. Employee training is ongoing from year to year. I have an Employee Training with a subform showing only the specific employee's training. I need a help with a few things. I need to keep track of training by the year. If I enter 2006 dates it will show in one line, if 2007 dates, another, all the way across the list of training classes for an employee. I also only want to limit a person enter more than one date for a particular class for a calendar year...Are these things possible. I have attached the database. Please help, make changes and suggestions. Thank you so much in advance.:eek:
I知 new here so don稚 shoot me if I知 asking something that is inappropriate. I知 looking to make a DB for paper file tracking simular as you would expect in a law firm.
I don稚 want to reinvent the wheel so I知 asking if someone has built something like this before. I知 also looking at barcode ID which I have no experience with at all.
Is there someone out there that can put me on the right path?
I've had a bit of a search around the forums and haven't found this anywhere.
Does anyone have a sample issue tracking database for an IT department?
I don't have too much Access experience so am looking for a little bit of a headstart on this. It seems relatively basic though.
The fields I think I will be needing are the following:
Log No Status Priority Type Project Raised by Person Raised by Department Description of Issue
Status 1 Active 2 On-Going 3 Hold 4 Finished 5 Cancelled
Priority 1 High 2 Medium 3 Low
Type 1 Bug 2 Enhancement 3 Other
Project 1 Lotus Notes 2 File Maker 3 Tumbleweed 4 Windows 5 Microsoft Word 6 Microsoft Excel 7 Microsoft Outlook 8 Adobe Acrobat
Raised by Department 1 Research & Development 2 Customer Service 3 Finance 4 Data Solutions 5 Communication Services 6 Production 7 Stores 8 Operations 9 Other
Would like to hear from anyone that has designed a database that can be used to track employee compensation on a year to year basis. I am current designing a database to do just that but I'm having a hard time deciding on how to setup the tables. What they use this for is yearly reviews so I need it to be able to pull data from prior years and the current year. I've designed one but don't think its going to work for me. Just interested to see if and how someone has done the same thing.
