Help with a Database

  • Thread starter Thread starter H. Hi
  • Start date Start date
H

H. Hi

Hi, I will like to know if somebody can help me with my database that I
created, the probles is that when I input the information of an employee that
previously was inputed in date before, the new information erase the older
ank keep only the new input data.

How can I make possible to keep all the information updated and allow
repetitive employee ID# without lost the previously information?

Thank you for your help.

Have a SAFE day!
 
We aren't there. We can't see what you're working with. We have no way to
know how your database is set up. We don't know how you are inputting your
data.

Specific descriptions are more likely to get specific suggestions.

Regards

Jeff Boyce
Microsoft Office/Access MVP
 
Hi, I will like to know if somebody can help me with my database that I
created, the probles is that when I input the information of an employee that
previously was inputed in date before, the new information erase the older
ank keep only the new input data.

How can I make possible to keep all the information updated and allow
repetitive employee ID# without lost the previously information?

Thank you for your help.

Have a SAFE day!

It sounds like you're overwriting the existing record instead of moving to a
new record, or that your table structure is incorrect. Since we cannot see
your tables, nor do we know how you're inputting the data, it's hard go be
specific. More info please?

John W. Vinson [MVP]
 
My table look like this:

ID- Autonumber
Employee ID- Number
Last Name- Text
Name- Text
Date of Hire- Date/Time
Post Accident Type- Text
Date Tested- Date/Time
Date Cleared- Date/Time
Date of CDL Physical- Date/Time
Date of next CDL Physical- Date/Time
Date of Training- Date/Time
Training Topic- Text
Safety Violation- Text
Date of Violation- Date/Time
Action Taken- Text
Month/Year- Text
Driver License Number- Text
Driver License Type- Text
Driver License Expiration- Date/Time

But when I input any information of any employee already in the table, the
old information is erased and just be able to show mw the new input that I
wrote.

Any idea?

Thasnk you.
 
How can I show you my table?


John W. Vinson said:
It sounds like you're overwriting the existing record instead of moving to a
new record, or that your table structure is incorrect. Since we cannot see
your tables, nor do we know how you're inputting the data, it's hard go be
specific. More info please?

John W. Vinson [MVP]
 
Let's see if I understand your situation...

You have a table with the information you show below.

You find a record in the table that belongs to an employee (with all that
employee's info).

Then you type over the information that goes for that employee.

And you're wondering where the old information went?

Are you saying you want to KEEP the old information, PLUS add the new
information? If so, you need a different table design.

In fact, with that many "Date-of-xxx" fields, you need a different table
design anyway -- this design looks more like a spreadsheet than a relational
table.

Good luck!

Regards

Jeff Boyce
Microsoft Office/Access MVP
 
Sorry by my English, I hope you understand me.
Yes, this is my problem when using a differents dates the old iinformation
is overwriting with the new one and don't be able to keep as a record.

You stated that look like a Spredasheet and I agree with you,can you help me
to create a different Table that allow this kind of information and be able
to track to verify the data that I inputed.?
How many tables I need to design or givme any idea to clarify my error.

Thank you for your help.

Have a Safe day!
 
How can I make possible to keep all the information updated and allow
repetitive employee ID# without lost the previously information?

You need to separate the constant information about the employee from the
variable information about the time-specific events, into at least two
separate tables in a one to many relationship. I don't know your business
model but perhaps:

EMPLOYEES
Employee ID- Number, Primary Key
Last Name- Text
Name- Text <should be FirstName, Name is a reserved word>
Date of Hire- Date/Time
Driver License Number- Text
Driver License Type- Text
Driver License Expiration- Date/Time

ACCIDENTS
Post Accident Type- Text
Date Tested- Date/Time
Date Cleared- Date/Time
Date of CDL Physical- Date/Time
Date of next CDL Physical- Date/Time
Date of Training- Date/Time
Training Topic- Text
Safety Violation- Text
Date of Violation- Date/Time
Action Taken- Text
Month/Year- Text <<REMOVE THIS, it's redundant; get it from the date field>>

If Accidents are one kind of event, Physicals a different kind of event, and
Training yet a third, then you need a separate table for each. You're using a
relational database - use it relationally!!

You may want to look at the tutorials and other resources here:

Jeff Conrad's resources page:
http://www.accessmvp.com/JConrad/accessjunkie/resources.html

The Access Web resources page:
http://www.mvps.org/access/resources/index.html

A free tutorial written by Crystal (MS Access MVP):
http://allenbrowne.com/casu-22.html

MVP Allen Browne's tutorials:
http://allenbrowne.com/links.html#Tutorials

John W. Vinson [MVP]
 
John V. offered a potential table structure.

You will need to spend the time to learn about normalization and relational
database design if you want to make best use of the features and functions
offered by Access.

Or maybe what you want to do could be done without needing to use a
relational database (i.e., Access)?

Regards

Jeff Boyce
Microsoft Office/Access MVP
 
Back
Top