Re: Documents in Database
- From: "Phill. W" <P.A.Ward@xxxxxxxxxxxxxxxxxxx>
- Date: Thu, 11 Aug 2005 16:08:36 +0100
"Q" <Q@xxxxxxxxx> wrote in message
news:uDBaM7nnFHA.3568@xxxxxxxxxxxxxxxxxxxxxxx
> I want to store all kind of files (pdf, doc, xls, txt) in a database.
> This is no problem.
I find it is often /easier/ to work with such files when they are safely
out in the file system!
> The real problem is opening the files from within a .Net application.
> I tried several ways to do it:
> 1. Creating an object of e.g. word to open a document.
> 2. Taking care of the problem through processes. --> create a process
> and run an instance of word...
3. Get the file out of the database, into the file system, and use
Process.Start to launch the document /itself/, thereby invoking the user's
default application for that type of document.
> these solutions have the same problems. If word is already open
> when you create the object (or the process) and you close
> it afterwards, the documents that were already open are closed also
> (and changes are lost)
Your problem is not in opening the document, but in knowing just
/when/ the user has finished mucking about with it.
Is your application waiting for the Start'ed (editor) process to end?
That would /help/, although it might be waiting a very long time before
the user closed down something like Word.
Take a step back from the technical nitty-gritty for a moment
- What is it you're hoping to achieve with this?
Regards,
Phill W.
.
- Follow-Ups:
- Re: Documents in Database
- From: Q
- Re: Documents in Database
- References:
- Documents in Database
- From: Q
- Documents in Database
- Prev by Date: Re: open .NET shell programmatically
- Next by Date: Re: copying code of event of user control automatically
- Previous by thread: Documents in Database
- Next by thread: Re: Documents in Database
- Index(es):
Relevant Pages
|