I have a standard WinForms application that connects to SQL Server. The application allows users to upload documents that are currently stored in the database to a table using an image column.
I need to change this approach so that documents are saved as files and the link to the file is stored in the database table.
Using the current approach - when a user downloads a document, he is protected from how it is stored, since they have a database connection, they donβt need to know anything about where the files are stored, no special permissions on directories, etc. necessary. If I set up a network resource for documents, I want to avoid any problems with IT, such as users who have access to this directory for downloading or access to existing documents.
What are the options for this? I was thinking of a temporary database where the documents are uploaded the same way as the current approach, and then the process running on the server to save them to the file vault. Then this database could be deleted and recreated to restore any space. Are there any more efficient approaches?
MORE INFO: There is no web server element in my application, so I donβt think WCF service is possible
source
share