G
gordontroy
I am trying to find out why Word 2007 Beta worked fine and now that I have
installed the 60 Day Trial of Word 2007 version (waiting for my license
keys), I am having a problem. We access Word documents off of a network drive
using the full UNC path (\\server name\shared directory\... not the mapped
network directory x:\directory\..) which is all maintained inside a SQL
database application. When we try to access the files from within the
database program, it thinks that the documents are in use by another user
(when they are not) and forces a Read Only open of the file. If I try to open
the document directly from Explorer off the network drive, using the full UNC
path, it opens with the read only mode, but if I open it via the mapped
network directory it opens fine. This has just shown up as we are starting to
deploy Office 2007 release version and was not a problem in the Beta. Is
there some registry setting that can be set to override this? or is there
something else that is different between the Beta and the trial release that
is causing this problem? As a temporary solution, we could live with the
assumption that the document is not in use by another user EVER, because it
very rarely ever happens that 2 people could or would be in the same document
at the sametime (just the nature of what we are doing). Any help on this
would be appreciated.
installed the 60 Day Trial of Word 2007 version (waiting for my license
keys), I am having a problem. We access Word documents off of a network drive
using the full UNC path (\\server name\shared directory\... not the mapped
network directory x:\directory\..) which is all maintained inside a SQL
database application. When we try to access the files from within the
database program, it thinks that the documents are in use by another user
(when they are not) and forces a Read Only open of the file. If I try to open
the document directly from Explorer off the network drive, using the full UNC
path, it opens with the read only mode, but if I open it via the mapped
network directory it opens fine. This has just shown up as we are starting to
deploy Office 2007 release version and was not a problem in the Beta. Is
there some registry setting that can be set to override this? or is there
something else that is different between the Beta and the trial release that
is causing this problem? As a temporary solution, we could live with the
assumption that the document is not in use by another user EVER, because it
very rarely ever happens that 2 people could or would be in the same document
at the sametime (just the nature of what we are doing). Any help on this
would be appreciated.