Yatiman Idara
Registered User.
- Local time
- Yesterday, 19:59
- Joined
- Apr 22, 2016
- Messages
- 27
:banghead:
Hi everyone,
I am currently working on a database. There are about 25,000 to 50,000 entries in this database and due to management requirements we need to store a profile picture for each of the entries
Now obviously this presents a difficult problem due to Access's 2gb size limit.
I am exploring some work arounds and wanted people's guidance and any ideas.
At the moment I have two ideas in mind:
1) Linking picture files - Saving all the profile pictures in a separate folder according to the ID number and then simply linking them to the field. That way they don't take up any space in Access as are stored externally. One drawback is that I expect the path to change sometimes so that would mean re-linking all of them everytime I change the network path.
2) Separate DB for pictures - Another method would be to create a separate DB for only containing profile pictures and then link that DB to my frontend. Drawbacks, never done it before and wonder if it will work smoothly with my main backend. Also as the pictures pertain to my main tables but are stored separately, does that mean I need to run my main forms off a query instead of directly from the table?
Thoughts, guidance and ideas are welcome.
Thanks
Hi everyone,
I am currently working on a database. There are about 25,000 to 50,000 entries in this database and due to management requirements we need to store a profile picture for each of the entries
Now obviously this presents a difficult problem due to Access's 2gb size limit.
I am exploring some work arounds and wanted people's guidance and any ideas.
At the moment I have two ideas in mind:
1) Linking picture files - Saving all the profile pictures in a separate folder according to the ID number and then simply linking them to the field. That way they don't take up any space in Access as are stored externally. One drawback is that I expect the path to change sometimes so that would mean re-linking all of them everytime I change the network path.
2) Separate DB for pictures - Another method would be to create a separate DB for only containing profile pictures and then link that DB to my frontend. Drawbacks, never done it before and wonder if it will work smoothly with my main backend. Also as the pictures pertain to my main tables but are stored separately, does that mean I need to run my main forms off a query instead of directly from the table?
Thoughts, guidance and ideas are welcome.
Thanks