Karen

> The files are only small, less than 100K.
> 
> I wrote the SP so yes I can change it.  But, I have no idea how to go about
> the web server route (I'm really not a techie!)  It sounds like a better
> route.

I have used variations on Jacob Gilley's Pure ASP File Upload script many times with great success: <http://www.asp101.com/articles/jacob/scriptupload.asp>. If you use the example provided, you may well be able to figure it out without drama. If not, you will need to resport to an ASP developer.

Solution 1
----------
Once you have successfully used the upload script to save the file to the Web Server file system, you will need to read the contents using the FileSystemObject and TextStreamObject, save the file contents to a variable, delete the file that you uploaded from the Web Server file system, and then build and run your SQL.

Solution 2
----------
The alternative is to upload the file to webserver via HTTP, save the contents to the database as a BLOB, and then use SQL Server to output the BLOB to the local filesystem (note: I suspect this is possible, but don't know exactly how to do it offhand).

The latter still requires the uploading of the file; ie the difficult bit of solution 1); so solution 1) is probably the best. I would imagine that the automation of the ftp solution would be a bit of the non-starter unless you want to delve into the world of Perl or some other CGI technology.

HTH

Regards

Chris Marsh

"Cthulhu for President. Why vote for a lesser evil?" --Cthulhu.org