The way that I have done it in the past, given this
scenario, is to persist the word doc to the File System
and only keep the UNC path in the database. Then I use
the FileSystemObject to grab the file and manipulate it,
pass it to the Client's web browser, etc...
Alternatively, you could store the word doc as in its own
table ensuring a column exists with the text datatype.
You can then subcategorize them by application if you need
that granular distinction. Then you must utilize Full-
Text indexing on the text column or it won't be indexed
and you can't keyword search it. SQL limits column lengths
to 900 characters for an index, unless it is full-text,
which on a single instance of a text datatype, you could
>I have an application which runs on two different servers
>(within and outside the firewall). But the database it
>connects to is same.
>I used to upload documents (ms-word, excel etc) on this
>server using aspupload. But now that there are two copies
>of the application running (within and outside the
>firewall), I can't do this anymore.
>So, I wish to upload these documents onto the sql server
>I wish to do this using asp scripts.
>If anyone knows this and can tell me how to do this, it
>would be a great help.