PrissySC wrote:
Is there a better way (xml) that would prove to be better? Space is not an issue; however, length of time to display is, as always, a major factor.
That of course depends on how the user is accessing it.
PrissySC wrote:
I would save as a file and link to the file, but I fear that in the manner suggested they will not map the network drive to a consistent letter at all workstations.
Again this depends on how the users access it.
PrissySC wrote:
What have you done or would you do?
Depends on the system but at least one file based solution is to provide an application\web server which can return a file URL and where the server permissions allow only for read only access into the file system. The database then returns something that can be massaged into a file url. There are other solutions and other factors such as how many files, what sort of access, how often does access occur, size of files, goals of project, etc.