Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!jarthur!watson!ssdken From: ssdken@watson.Claremont.EDU (Ken Nelson) Newsgroups: comp.sources.wanted Subject: Re: Time reporting tools (automated timesheets!) Message-ID: <8063@jarthur.Claremont.EDU> Date: 8 Aug 90 19:58:31 GMT References: Sender: news@jarthur.Claremont.EDU Reply-To: ssdken@watson.Claremont.EDU (Ken Nelson) Lines: 48 In article , larry@focsys.uucp (Larry Williamson) writes: |> |> I want to automate our archaic, manual timesheet system. |> |> Every week we have to fill out these silly paper(!) forms reporting |> how much time we spent on which projects. Then someone must type all |> this info in to some other system. |> |> This is crazy. |> |> It does not much matter how we enter the data, it would be nice simply |> to be able to type it in every day and have the results posted to the |> proper authorities each week. |> |> It may be based on |> . a database (informix for example) |> . a spreadsheet (sco professional (lotus look-a-like) for example) |> . flat ascii files created by shell scripts and processed by awk or |> perl or ?? |> . ?? |> It seems to me that any system must have access to whatever system that "other person" is entering the data into. So, if you have access why not have everybody just type it directly into the system the "other person" is typing it into. If that is not feasible, then I imagine a system could be fashioned out of any of the approaches you mentioned. But they would still require some kind of access to the final time tracking system. AWK would do it very easily using associative arrays indexed by project names etc..... Good luck, Ken Nelson Principal Engineer Software Systems Design 3627 Padua Av. Claremont, CA 91711 (714) 624-3402