• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

building a simple (?) timesheet app with Excel

Biggerhammer

Golden Member
I'm trying to put together a simple timesheet app for my office. It doesn't need to track payroll (that's covered on paper), but it will let the boss see what the clerks are doing during the day- ie, Bill spent four hours on project X, three hours on project Y, one hour filling out paperwork such as this timesheet app.

My concept is an Excel spreadheet where Bill selects project X from a dropdown, puts in four hours, and hits update. The update button (which will probably make me dust off my old VB skills) will figure out which lines are new, copy them, and paste them into another spreadsheet. The boss will use that spreadsheet.

I'm using multiple Excel spreadsheets because the servers here are set up so that it is diffficult for more than one user to simultaneously use an Access DB. If I could change the servers, I would do this with a form in Access but the environment limits me.

Anyone know of sample code that copies lines from one spreadsheet and pastes them into another?

Thank you.
 
I'm using multiple Excel spreadsheets because the servers here are set up so that it is diffficult for more than one user to simultaneously use an Access DB. If I could change the servers, I would do this with a form in Access but the environment limits me.

That makes no sense. If 2 users can use the same excel sheet, then 2 users can use the same DB. The network layer doesn't care (or know really) if a DB or XLS file is being accessed. Even if there was such a constraint, access is a better option. You can get around this phantom limitation by divorcing the form and table. Create one access db that only contains the final table. Then create another db with a linked table to the db with the actual table, and put the form in with that. Then you have 2 DB's; one with data, one with a form and link to the data.
 
The clerk's spreadsheet should be able to have multiple instances- ie Bill has a Bill's sheet.xlsx, Claire has a Claire's sheet.xlsx, etc. there would be just one master sheet that received the data from all the clerks.
 
Back
Top