You have a Server A which produces the reports.
You have a Server B where you want the reports to be.
So obviously you will need to move them. You will need some sort of scheduled process that moves them via some sort of protocol. I would suggest figuring out what you want to do with the file on Server A after you have successfully moved it also.
None of the above has anything to do with a user.
Now maybe the problem is that you have not actually identified yet that you even need a Server B.
But I suspect you probably would want that because "database application" suggests a "database" and myself I do not want anyone but my stuff touching the database server.
So given that you have a Server B then you need to define HOW you are going to serve those files (doesn't matter what is in them) to a user. There are all sorts of considerations. Some of the ones I can think of.
- How does the user know which file they are looking at
- How do you insure that user A doesn't see user B's reports
- How do you actually serve up the file. Do you just down load it or do you want do have it pop open?
- Are they downloading one file at a time or many?
- What happens to the old reports on Server B?
Notice that none of the above has anything to do with Server A.