Table structure for salary

[Harrold]

Hi

I can think of:

tblSalary
ID(PK autonumber)
EmployeeID(FK)
PayPeriod(FK)
SalaryAmount

tblPayPeriod
ID(PK autonumber)
PayPeriod (eg, Jan 2011, Feb 2011,etc)

i know something is not right, i believe i need another table as junction table. But i dont know what to include in it. Can someone please advice?

Thanks a million

 

[vbaInet]

Harrold,

You haven't explained what your objective is or what the Salary table is for.

 

[Harrold]

i have been put in the role of preparing payroll and hence trying to use access to do the job. that means the report will be the final output to show to the boss what is the amount need to pay out to each employee in current month.

Salary table is to store monthly salary of each employee which include historical amount. Salary table is only part of the whole table structure. I will include commission, deduction, staff advance, etc in other tables. I am still in the middle of constructing the whole table structure.

Thanks

 

[spikepl]

Not to dampen your enthusiasm, but prior to undertaking such work the sensible thing to do is to ask the following question: Is our problem so unique that it requires developing a system for that, or can we get/buy/rent something that can do the job? Payroll is a a fairly basic ingredient in any business - millions of them - and supported and verified commercial off-the-shelf-systems exist for that. Developing anything is expensive - especially in subsequent maintenance/expansion, and if the original developer has moved on.

 

[Harrold]

ours is just a simple one. in the past, my predecessor use manual (calculator) to come out with the final figure. and then just plug that figure into excel and print out a report.

to me, i would like to try it at Access. i am always interested to learn new skills which can improve my work effiencency. Hopefully, i can get support from experts on this forum to reach my goal.

Thanks

 

[vbaInet]

A Payroll database is not a simple one to tackle as a beginner because there are so many intricacies. I don't think anyone on here will be able to (or willing to) guide you from start to finish of how to develop a payroll system. You may think your Payroll system is simple enough but payroll is payroll, it's not easy and not something a beginner should build to handle other people's monthly wages.

Tell your boss to invest in a small payroll package and maybe you can learn from how it was built and then build your own.

 

[Harrold]

as mentioned, it is my interest to learn. i am building the database, when i have queries then i post my questions here.

I dont understand why cant the original question be answered. I am not asking for someone to provide me with the whole payroll design. I am doing it small step at a time and once done, i will test it to see whether it is workable or not.

As commented by spikepl and vbaInet, it is not an easy task. but i am really interested to give it a try. if not for work, it can be treated as a hobby. So i will be grateful if someone can take some time to read my original question and advise me accordingly.

Thanks ;-)

 

[jdraw]

Harrold,

It is obvious from your post that you are intent to build or try to build a payroll system. Your interest and enthusiasm are to be praised. However, it isn't that your question was not answered, but that you were given advice based on the information provided.

Before getting comments on the structure of your 2 tables, basically out of any business context, I recommend you do a little research into payrolls; pros and cons of building such a system in house; legal obligations of a payroll system in your country/region; etc. to clarify the scope of your project and to gain some recognition of issues that you may or may not have considered.

I did a google search and found things like this
http://www.ehow.com/info_7869169_requirements-payroll-system.html
http://www.ehow.com/how_7177758_make-flow-chart-payroll-system.html
http://www.halfpricesoft.com/small-business-payroll-tips.asp
http://ezinearticles.com/?Small-Bus...ons-of-an-in-House-Payroll-Systems&id=4480693

This is not meant to dissuade you, but to put more context on your project and question. Good luck with your project.