payroll help

[oldham94l]

i've been given the task of creating a payroll system for 30+ stores,
each store can have from 30 to 70 staff which are constantly being removed and added to.
and then each week i will need to combine all the data from each store at our headoffice.
could you advise me on the best file system for this format?
and the best way to organise employee names and numbers?

thanks

 

[George J]

I would have 31 sheets. 1 for each store and make the first sheet the head office.

Have a header row at the top.

Employee name ____ Staff no. ____ Position ___ etc

And keep this uniform for each sheet.
Easiest way is to get the layout onto 1 sheet then copy that sheet 30 or so times. Saves all that typing. The board will be able to advise on formulas or macros you may require to collate all the required info for the head office sheet.

Hope this gets you started.



_________________
George J
This message was edited by George J on 2002-09-06 15:50

 

[MarkHenri]

I'm partial to Oracle though SQL Server costs quite a bit less and is very fast. If you want the rock bottom price, MySQL is an excellent choice though they don't support triggers or views. I would avoid Microsoft Access for this application because it lacks the robustness.

As an alternative, I would suggest using a service such as Paychex. They handle all the processing, you just phone in your employee hours and they prepare everything. The cost is very reasonable and they handle all the changes in the tax laws that occur every year.

This would be considered an advanced application. Normally companies hire consulting firms to design and implement software systems like this. I wouldn't attempt this without a thorough understanding of database issues and programming concepts. Experience also plays into the success of a software project. Companies like www.swingnote.com specialize in creating business solutions such as this and have years of experience.

 

[wildman]

I agree msaccess cant handle large amounts of data. I am forever having to split the data to get it through access. Go with syabse, oracle , or mysql mysql is free gnu for linux or unix.

 

[MarkHenri]

Not only do I mean that Access lack the ability to handle large volumes of data, but it's error recovery is not very sophisticated. It uses open file handles across a network. A client machine crash can break the file system.

Conversely, if you pull the plug on a server running Oracle, it will come right back up to the last transaction if configured properly.

I use robustness in the sense that it's strong in every sense. When doing payroll for a medium sized business such as this, your data must be protected. Access or Excel lack the necessary safeguards to do this and were not intended for this sort of task.