A
A.Karim
Is there any conflict when Microsoft said in the document :
Creating a Managed Code PDS Extension for Project Server 2003.
http://msdn.microsoft.com/library/d..._pj2003_ta/html/ODC_BuildPDSExtension_NET.asp
In section : (Accessing Project Server Data)
It says : "The Project Server 2003 database can be accessed directly using
ADO and an appropriate SQL Server connection string. This access method is
not recommended as a best practice for a number of reasons:"
and one of thier reasons were:
"Direct database access does not sufficiently abstract the data storage from
the client view. A client that relies on direct database access will not be
compatible with future versions of Project Server."
And in the same document in the Section:
Case Study: (A Stored Procedure Wrapper)
When they used a Stored Procedure reading from a View and that view is made
from Project Server database tables.
where reading from direct database tables means direct access
How this would keep the compatibility if a new release changed the database
structure.
Creating a Managed Code PDS Extension for Project Server 2003.
http://msdn.microsoft.com/library/d..._pj2003_ta/html/ODC_BuildPDSExtension_NET.asp
In section : (Accessing Project Server Data)
It says : "The Project Server 2003 database can be accessed directly using
ADO and an appropriate SQL Server connection string. This access method is
not recommended as a best practice for a number of reasons:"
and one of thier reasons were:
"Direct database access does not sufficiently abstract the data storage from
the client view. A client that relies on direct database access will not be
compatible with future versions of Project Server."
And in the same document in the Section:
Case Study: (A Stored Procedure Wrapper)
When they used a Stored Procedure reading from a View and that view is made
from Project Server database tables.
where reading from direct database tables means direct access
How this would keep the compatibility if a new release changed the database
structure.