Any Reason NOT to Provide (Publish) Application Only AvailableOnline?

All,

I could use some big-picture guidance here. I have written a timer
application for 35 users. I was originally planning to have the
application installed on each user's PC, but now I'm wondering if I
can skip that - and some headache.

The application essentially starts a timer when the user clicks a
button, stops the timer when they click the next button, then creates
an XML file on the user's PC, and writes a copy of the info in an
MDB. The MDB is stored on a user's mapped drive for one day.

Is there any good reason NOT to publish the application as "only
available online" instead of installing it on each user's PCs? They
can't run it when not connected to the network anyway, because they
need access to the MDB.

Am I shortchanging something somewhere or doing something dangerous?
Seems easier to me, especially when it comes time to update the app,

Thanks,

Patrick