Hyperlinks vs. Files
Page: 1
Hey Guys,
we are working with a lot of technical instruments in my business. Every project we run uses a determined combination of some of those instruments. What I need to do is to add the correspondent manuals and sales literature as files to every project.
So my question is: which way would you suggest to provide the correspondent documents to every project without uploading them every time again (for redundancy and space reason). I thought on hyperlinks instead of files.
To have one project with all the files where project staff goes to to look up the right document is not an alternative - documentation is too vast for this.
So my thought is: can I put a pointer (link) to a file in the activecollab-file-system instead of uploading the same file for every project?
Would be perfect to see the "file" in the file-section of the project, but to not have a file behind this, but just a link.
Curious for the answer
Chris (using the paid hosted demo at the moment)
we are working with a lot of technical instruments in my business. Every project we run uses a determined combination of some of those instruments. What I need to do is to add the correspondent manuals and sales literature as files to every project.
So my question is: which way would you suggest to provide the correspondent documents to every project without uploading them every time again (for redundancy and space reason). I thought on hyperlinks instead of files.
To have one project with all the files where project staff goes to to look up the right document is not an alternative - documentation is too vast for this.
So my thought is: can I put a pointer (link) to a file in the activecollab-file-system instead of uploading the same file for every project?
Would be perfect to see the "file" in the file-section of the project, but to not have a file behind this, but just a link.
Curious for the answer
Chris (using the paid hosted demo at the moment)



