S
Shane
Since the project server system doesn't seamlessly allow consolidated
schedules in the database, we create consolidated schedules by creating stand
alone .mpp files, then inserting schedules from the project server (read
only). When we open Project, then open the .mpp, everything loads fine. If we
double-click on the .mpp file in File Explorer, everything loads fine.
However, if I create a webpage, and on that webpage I put a hyperlink that
points to that .mpp file, when I click on that hyperlink it loads Project and
loads the .mpp file, but when it attempts to insert the project server files,
I get an SQL Server login box. It appears to loose the authentication that
project server uses to connect to the SQL Server database.
The odd thing is that this concept worked fine in 2002. But when we upgraded
to 2003, we lost this capability. Is this true that 2003 did something to
remove this capability, or did we miss something when we upgraded?
Thanks.
schedules in the database, we create consolidated schedules by creating stand
alone .mpp files, then inserting schedules from the project server (read
only). When we open Project, then open the .mpp, everything loads fine. If we
double-click on the .mpp file in File Explorer, everything loads fine.
However, if I create a webpage, and on that webpage I put a hyperlink that
points to that .mpp file, when I click on that hyperlink it loads Project and
loads the .mpp file, but when it attempts to insert the project server files,
I get an SQL Server login box. It appears to loose the authentication that
project server uses to connect to the SQL Server database.
The odd thing is that this concept worked fine in 2002. But when we upgraded
to 2003, we lost this capability. Is this true that 2003 did something to
remove this capability, or did we miss something when we upgraded?
Thanks.