P
Paul
Hi,
I am assessing a spec that I have been given to create a document managment
database with some task scheduling capabilities.
The database will be created in SQL Server. Essentially each document
(record) will have a review date, an owner, and a time required to complete
the review.
The spec requires some quite sophisticated scheduling (e.g. resource
levelling, reporting, calendar views and notifications). Instead of building
this into the application I would prefer to link the 'document db' to
Project.
I have read a little and my understanding is that the best way to do this
would be to create a small vb app (left running on a server) that would.
1. Use ADO to link to 'document db' and MS Project (what is the db engine
for single user project?)
2. On a regular basis check that each document's review task exists in
Project
2a If it does, update the review date ('Task must be completed by' date
and other relevant fields in Project)
2b If it does not exist, create the task in Project db and capture the
Task ID and record this against the document record.
3. Update some key details in the document db (Task start date, end date, %
complete) if required
4. I may also have to do something similar with document owners,
automatically adding them as resources and linking them to the
imported/updated task (document review) as appropriate..
Is this the best way to go about this?
Are there any documents detailing how to do this/case studies of where this
sort of thing has been done (I have downloaded the Project data structure
from MS)?
If there is a vb class module for checking/updating/inserting tasks into
Project dbs that would save me creating my own ;-)
I am a pretty competent SQL Server and VB developer with a fair amount of
experience linking the two via ADO. I have very basic Project skills and
ideally the solution will not require me to code anything in Project itself.
As a very rough estimate to put on my assessment, I would give the above 5
days to implement (erring on the side of caution as I am unfamiliar with
working with the Project back end). Does this sound realistic (I think only
a few details will need to pass back and forth between the databases)?
Thanks
Paul
I am assessing a spec that I have been given to create a document managment
database with some task scheduling capabilities.
The database will be created in SQL Server. Essentially each document
(record) will have a review date, an owner, and a time required to complete
the review.
The spec requires some quite sophisticated scheduling (e.g. resource
levelling, reporting, calendar views and notifications). Instead of building
this into the application I would prefer to link the 'document db' to
Project.
I have read a little and my understanding is that the best way to do this
would be to create a small vb app (left running on a server) that would.
1. Use ADO to link to 'document db' and MS Project (what is the db engine
for single user project?)
2. On a regular basis check that each document's review task exists in
Project
2a If it does, update the review date ('Task must be completed by' date
and other relevant fields in Project)
2b If it does not exist, create the task in Project db and capture the
Task ID and record this against the document record.
3. Update some key details in the document db (Task start date, end date, %
complete) if required
4. I may also have to do something similar with document owners,
automatically adding them as resources and linking them to the
imported/updated task (document review) as appropriate..
Is this the best way to go about this?
Are there any documents detailing how to do this/case studies of where this
sort of thing has been done (I have downloaded the Project data structure
from MS)?
If there is a vb class module for checking/updating/inserting tasks into
Project dbs that would save me creating my own ;-)
I am a pretty competent SQL Server and VB developer with a fair amount of
experience linking the two via ADO. I have very basic Project skills and
ideally the solution will not require me to code anything in Project itself.
As a very rough estimate to put on my assessment, I would give the above 5
days to implement (erring on the side of caution as I am unfamiliar with
working with the Project back end). Does this sound realistic (I think only
a few details will need to pass back and forth between the databases)?
Thanks
Paul