Or anyone has any suggestions? My intention
is to use Exchange/Outlook for TimeSheet.
And just an easy and quick solution.
Thank you so very much,
calvin
Think of how you yourself would enter time - you'd probably expect to open a
form that at least displayed a week grid beginning on the first day of the
current week. This requires coding to set the labels correctly. It would
be nice if you could scroll to the previous week to remind yourself what you
did - a fair amount of code for an Outlook form. If you get into providing
job codes that must be used, then maintaining and presenting these requires
even more code. Of course then there are timesheet printouts - a ton of
code and integration to make this acceptable from an Outlook form!
Timesheet systems quickly go beyond quick and easy.
Usually all the data you collect is best served being in a RDBMS for the
inevitable queries that have yet to be thought of. Exchange/Outlook are
hierarchical dbs. This may bring into question the need for Outlook at all
if all data is already in a database. I understand the desire to have it in
Outlook and easily accessible from people's email and other apps. A
straight Outlook/Access solution will require more code than you are
thinking - and the final product will contain limitations that may be
incapable of resolution within Outlook. You'll also have to setup ODBC
drivers on each workstation to make this work - and/or build some custom
event scripts on the Exchange folder or with OL2000 using its folder events
to ferry data to/from the db. To alleviate possible limitations, and to
keep the system within Outlook, consider creating a VB app to do this and
publishing it to Exchange/Outlook with mPower98 from SaxSoft:
http://www.saxsoft.com
Bottom line: My suggestion is to not do this in Outlook and to create a
web-based intranet timesheet app using ASP. This way the server is the only
one needing an ODBC driver, most limitations are avoided and totally
controlled by your ASP code, reports are a breeze, etc., etc., etc.
However, this is still not quick and easy - it requires more code than you
think.
Good luck,
Todd Reavis
tre...@ecommercelabs.com
Calvin SK Kee <cal...@singnet.com.sg> wrote in message
news:7jj5ph$am7$1...@violet.singnet.com.sg...
http://officeupdate.microsoft.com/downloadDetails/timecard.htm
Hal
--
Hal Hostetler, CPBE -- h...@kvoa.com
Senior Engineer/MIS -- MS MVP-DTS -- WA7BGX
http://www.kvoa.com -- "When News breaks, we fix it!"
http://home.nbcin.com -- NBC Interactive Neighborhood
KVOA Television, Tucson, AZ. NBC NBC-IN
i am thinking of selling this solution (once it's ready, which will be in a
few weeks) , of course i plan to optimize it on the customers wishes,
therefore, if you are interested tell me which features you would need and
tell me how much you'd like to pay and let's talk.
(if you'd like the database and outlookformular on an as-is-basis to develop
your own solution mail me as well - currently it is in german, therefore i'd
have to ask you for a small donation there as well, but well, let's talk)
CU
Mike Beck
webm...@ibmiller.de
http://www.mikrocosm.de
http://www.ibmiller.de
Calvin SK Kee <cal...@singnet.com.sg> schrieb in im Newsbeitrag: