PJDB.HTM

[Bettergains]

Hello: a question on the following taken from PJDB.htm

Note The information in this document does not always apply (or may be
different) for enterprise project data stored in the Microsoft Office Project
Server 2003 database. It is recommended that enterprise project data in the
Project Server database only be interacted with by using the Project Data
Service (PDS), Microsoft Office Project Professional 2003, or Microsoft
Office Project Web Access 2003.

Am I correct in interpreting this to say that if our projects are uploaded
to MPServer, we cannot expect to have success managing them from a local
access database? Or, alternatively, we CAN if they are first saved as .mpp's?

 

[Earl Lewis]

I think your assessment is accurate. You would have to analyze every table, view, stored procedure and trigger (and more I'm sure) to have any hope of being able to ensure that you're doing everything MSPS is taking care of under the covers.

Saving the files as MPPs confounds the imagination, not to mention defeating the purpose of using project SERVER in the first place. Maybe you could enlighten us about what you're trying to acheive.

Earl
Hello: a question on the following taken from PJDB.htm

Note The information in this document does not always apply (or may be
different) for enterprise project data stored in the Microsoft Office Project
Server 2003 database. It is recommended that enterprise project data in the
Project Server database only be interacted with by using the Project Data
Service (PDS), Microsoft Office Project Professional 2003, or Microsoft
Office Project Web Access 2003.

Am I correct in interpreting this to say that if our projects are uploaded
to MPServer, we cannot expect to have success managing them from a local
access database? Or, alternatively, we CAN if they are first saved as .mpp's?