Implementation Ideas for data entry project

[cbv]

Hello,

I am considering using MS to develop a data entry system for a web page.

As it is, every month, a user has to input the data of approx 100 printed out timesheets. Project numbers and associated hours are input.

Some of the timesheets have been hand written. Most have been entered and printed using Excel.

I'm looking for ideas on good approach/strategy in creating this solution.

I was thinking of scanning the printouts to pdfs. Then having MS read the pdfs and input the data to the web page.

Since this is a long term, low priority project, I am willing to learn and take on this project. Am I crazy? IDK. I don't know how much work is involved for this automation project.

I am also open to paying for a solution, depending on the cost.

Ideas?

[Marcus Tettmar]

Your mileage is going to vary when it comes to scanning handwritten sheets. Accuracy is going to be a problem. I'm not sure I would trust hand writing recognition in an unattended automated context.

[cbv]

Thanks for replying, Marcus.
I could make it a policy that all timesheets be handed in as Excel printouts.

Would it be easier, from a development point, to scan and read printed sheets? Or, to read Excel .xls files?

[Marcus Tettmar]

I would say reading from Excel files would be better/more reliable.

[Jerryth31]

If you have the authority to do so (and it sounds like you do), you can develop a template so that the data is in specific cells. Maybe even have a couple of cells that contain instructions or something that you could identify easily to ensure that the template has been used.
(If cell A1 not equal to "This template must be used for submitting...." then app will reject.)

Then your app can assume data entered in the correct locations.
Otherwise everybody is going to be just a little different in their layout & formatting.

[cbv]

Thanks, Marcus and Jerry.

Can anyone give a ball park price on developing this solution? Probably not but still asking anyway.

I'm just trying to see what's more cost effective.

[Jerryth31]

Price - need lots more details.

Another option instead of Excel, is build a data entry program that your users will have on their machines. It could write their times into a CSV file that your main app digests.
This has the advantage of not depending on Excel at all (what happens when some people have upgraded and some haven't, etc.) and allows to you to create a very professional looking app instead of "Load this template and fill in the data...".
(This can be compiled into an exe so no, every user wont need a copy of MS.)

A basic Time Card system shouldn't be very complicated.

[cbv]

Hi Jerry,

A replacement program. OK.

How would it look, interface-wise? With the current Excel worksheet, the users like the ability to 'browse' the grid sheet and see each days/week total and separate times entries.

Also, it has a lookup feature - when a project number is entered in a cell, a lookup for the related project title is done in another Excel worksheet. If found, the title is placed next to the number.

Can this be done similarly?

Excel Timesheet.png

[Jerryth31]

You could make it look very similar and even support the lookup into Excel for the project title.

I didn't realize you had it looking this polished already.
Not worth redoing if you don't have to at this point!

[cbv]

It's somewhat fancy. e.g. When you enter the date range in B2, e.g. 8/1 or 8/16, it automatically enters the days and formatting, i.e. shading / colors.