Hello,
on one of our customers sites we run a asp solution, where users share
documents on a central document store through our application. the uploaded
documents are stored in a central folder, named with a prefix (date+time)
and original document name, so that we get singular document names for each
document and can host duplicate document versions.
on showing the document in the web application the app copies the selected
document to a temporary folder and renames it to the origianal name, so that
the users gets it in the original condition.
with a response.redirect the web application delivers the document to the
client over the http protocol and the client opens the hosting application
(word, excel, powerpoint, acrobat reader, ...) and finally shows the
document for the user.

this works fine with pdf or graphics documents, but with office documents
the office client caching works contraproductive ... - office opens the
first document, which is in the client cache, this could mean, that the user
becomes not that one, he or she selected in application.

we tried to use various meta tags to tell the web server, that the web page
has to be reloaded, but this is no solution, because the web application has
always done the right thing. in the temporary folder is always the right
document version, but the client show eventually the wrong one, if there
already is a document with the same name, in the client cache.

does anybody know, how we can influence the way of working of the office
cache on the client????

the system environment we face at the customers site is:
quote:

> @Server:

- Windows 2000 Advanced Server English + SP3
- IIS5
quote:

> @Client:

- Windows 2000 German + SP3
- Office 2000 German + SP3
- IE 6.0 German + SP1

thanks for your advice!!!

yours, Christian

christian presslmayer
office-soltuions.at

[ Post a follow-up to this message ]