With the database I'm working on for someone I need to link images.
The way I see it there are two options:
1 Store the full path to the image (like d:\databases\movies\myfile.jpg)
or:
2 Store the path relative to the backend location (\movies\myfile.jpg)
Then concatenate the backend path and link to view the image.
I use option 2 on one of my applications and the advantage is
that the links stay valid no matter where the backend is located.
Option 1 will give the user a more freedom of where to store the images.
However, with any changes in location the links will break.
I could even give the user a choice of which option to use.
Does anyone have any thoughts about this?
All ideas will be greatly appreciated.
Catalina
The way I see it there are two options:
1 Store the full path to the image (like d:\databases\movies\myfile.jpg)
or:
2 Store the path relative to the backend location (\movies\myfile.jpg)
Then concatenate the backend path and link to view the image.
I use option 2 on one of my applications and the advantage is
that the links stay valid no matter where the backend is located.
Option 1 will give the user a more freedom of where to store the images.
However, with any changes in location the links will break.
I could even give the user a choice of which option to use.
Does anyone have any thoughts about this?
All ideas will be greatly appreciated.
Catalina