Saving and running Project in Database format

[John B]

Hi experts,

What are the pros and cons of running microsoft project in database format?

i am planning to create an Access Forms UI on top of MS project to allow
members to update their percentage complete.

The logic is that Access Forms allows more flexibility in terms of error
checking and automation. The people I am working with are very
inexperienced with PM tool and basically get confused if they see more than a
handlful of input boxes.

Also I am planning to create something like a portal using Access where
people see their assigned tasks when they enter the portal.

I realize there may be better way to do this but basically I have a day or 2
to do this and MS Office product is the only thing made available - no
project server, no database server, webssever. I have to hack this one
through.

any suggestions will be greatly appreciated!

John B

 

[Rod Gill]

Hi,

If you only have a day or two then don't do any solution!!

Saving in an Access database is fine, but updating information has to be
done very carefully and thoroughly and you need a good backup system!

With Access you MUST make sure each user has their own front end database
with forms and code only and only share the backend database. Sharing is
good, but if you don't do it properly and a database corrupts a lot of
schedules can get corrupted. You need thorough testing and handling of all
exceptions and 'funnies' that happen with users. You won't find all these in
2 days. Total effort if you know all that you need to and are expert with
Access and Project: I would allow at least a week's effort over a month to
get a stable system running.

Search the web for companion products that have time sheets for updating
schedules.