Unable to access documents

[fred]

Hi,

I have a new install of Project Servere 2003 SP2, WSS, SQL 2000 SP4 on Win
2003 SP1 (single server), installed in line with the single server install
guide.

Project seems to work fine, but users cannot save back or check in modified
documents (word, Excel etc). Word and Excel display file not found (or
similar) errors when trying to save back. Document libraries can be created
OK from within project, and projects themselves publish OK - there just seems
to be a permisions or name resolution issue for clients saving back to wss.

Any ideas?

Thanks,

fred

 

[Aaron Tamblyn]

What version of Word / Excel are you running?

 

[Ray McCoppin]

As Arron stated it is problabliy the version of Office that you are running.
Only Office 2003 with WSS can do a edit in place. Other version need to save
as then upload a new version of the document.

 

[Engelbert]

Only Office 2003 with WSS can do a edit in place

Possibly the right answer in this case but actually Office XP with WSS can
also do an Edit in place (using Edit in Microsoft Word on the menu line just
as Office 2003 does). Problems start (going backwards) with Office 2K.

Engelbert

 

[John Carter]

I don't know if this has any bearing on the subject or not but having been a
long time user of Project Central, then Server and the related PWA client I
can say that the user interface changed significantly between Project Server
2002 and 2003, as it relates to document libraries. The edit document icon,
which in the PWA 2002 client used to result in the edit document page, where
you could then select the edit document function, when clicked in the PWA
2003 client results in an error with a message indicating field not defined.
I don't know if this is your situation or not, but what we've found is that
the user interface simply has changed and now the way in which you access a
document is through the pull-down list that is visible from the TITLE field
linked to the document. This may be unique to my installation, but thought
that this might be common to users that have upgraded from a prior
version/rlse of the software.