aframiller326 (2/13/2014)
Jeff Moden (3/11/2013)
I'd have to include FileStream in the same bucket as the "File Path Reference" approach with some reservations. To be sure, I've not used FileStream, yet (too much on my plate for now), but I like what I see in the documentation. One of the things that would be important to me is that other applications should be able to save image[/url] in the data containers that FileStream uses without having to go through anything having to do with SQL Server or FileStream. For example, I'd like folks to be able to get to the files using only, say, Windows Explorer and be able to open up a PDF or a JPG or whatever just by double-clicking on it. I also need to be able to "update" the content of a file simply by replacing it through something as simple as the Command Prompt. If that can't be done in FileStream data containers directly (and I haven't found such explicit information in the documentation, yet), then file saving[/url] Filestream wouldn't work so well for the things I need to do.Right now, I am saving file in a table and I know it will suck when the image file size grows bigger. Thus, I am trying to find another way for storing image in sql server. And I am very interested in your file path reference approach. You mentioned the documentation and I wonder could you please recommend that documentation for me? so I can know more about this kind of file saving method. Thanks you so much.
Sorry for the late reply. The link behind the bold lettering in my previous reply apparently didn't work for click-ability. Here's the plain link for the "file path reference approach".
http://www.rasteredge.com/how-to/vb-net-imaging/open-save-file/
--Jeff Moden
Change is inevitable... Change for the better is not.