My Project working from ABCD - Microsoft Access ABCD


	Back to ABCD Comments List

Upload Images @Reply Bookmark Link Email Next Unseen

My Project working from ABCD

Ron VandeVelde

5 years ago

Mr. Rost,
As we have discussed a few times on email, I am working on a project where I need to create a database for tracking employee licenses. Our company has employees that require licensing by some of the States we work in. So here are some of the things I need to add to the database. For starters I will need a way to track each State that requires licenses, I would like to include the following:
State, Type of license required, License cost, license duration (usually 1, 2 or 3 years), contact person at the State, contact phone, fax and email, mailing address, possible satellite office. That is all of the State info I can think of right now. Then there is added information I need to add (I think) to the employee/person/entity table, I need to add which states they are licensed in, what type of license, date licensed, license expiration date, license # (can have more than 1 type/license # for a state), full-time, part-time, seasonal, hire date, termination date, rehire date. Right now that is all I can think of, my eyes are starting to cross. I had no idea that I had forgotten so much. BUT I am so happy to be diving back into working with databases....

	Richard Rost @Reply 5 years ago
You could set up each State as an Entity, then all of the info that you need to track (licenses required, etc.) can go into the Misc Data fields.

Ron VandeVelde OP @Reply

5 years ago

Are you saying to add each State to the existing EntityT that holds all of the Employees? Looking at ABCD-after-L7 database, it would be like the entry for EntityCode P265476? If so, then I would just add a new HelperTypeID that reflects 1) # of years of license (ex 1, 2 or 3)? Then also add a new HelperTypeID for the States?

I have added a HelperTypeID for the employment status (ex Full-Time, Part-Time, On Leave etc.). Then I have added columns to the PersonT for EmploymentStatus, HireDate, FireDate, LeaveDate...Does that sound like the best plan? Lastly, do I need to add a StateT table? Then (like the emailT) I could list numerus States for each employee.

I haven't gotten to the video where you change the PersonT to EntityT yet, I assume I will have a better understanding after I get to that video. As always, thank you so much for the guidance and very quick responses.

	Richard Rost @Reply 5 years ago
I'll have to take a closer look at your needs. I would wait until the Core is finished and then we can decide the best mode of attack for your database. You may want a custom StateT field for all of your requirements.

This thread is now CLOSED. If you wish to comment, start a NEW discussion in ABCD.

Next Unseen

New Feature: Comment Live View