In the sample demoattachment.nsb, pictures are stored inside this database. Storing pictures inside a database will make the database file very large, is it also possible to display pictures (or a thumbnail of them) inside a database by only linking them from a separate folder?
I would like to integrate a similar function into the assets database, to have pictures of assets, but I worry that the database will get too large very quickly.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, storing images in a database can make it big so what?
You can limit the size of images and their numbers by registration.
This composition also exists in MSAcces
You can manage your images yourself by links, but it is more complicated and referential integrity is difficult to maintain: deletion of image, renaming ...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, storing images in a database can make it big so what?
You can limit the size of images and their numbers by registration.
This composition also exists in MSAcces
You can manage your images yourself by links, but it is more complicated and referential integrity is difficult to maintain: deletion of image, renaming ...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In the sample demoattachment.nsb, pictures are stored inside this database. Storing pictures inside a database will make the database file very large, is it also possible to display pictures (or a thumbnail of them) inside a database by only linking them from a separate folder?
I would like to integrate a similar function into the assets database, to have pictures of assets, but I worry that the database will get too large very quickly.
Yes, storing images in a database can make it big so what?
You can limit the size of images and their numbers by registration.
This composition also exists in MSAcces
You can manage your images yourself by links, but it is more complicated and referential integrity is difficult to maintain: deletion of image, renaming ...
Yes, storing images in a database can make it big so what?
You can limit the size of images and their numbers by registration.
This composition also exists in MSAcces
You can manage your images yourself by links, but it is more complicated and referential integrity is difficult to maintain: deletion of image, renaming ...