Denise2020
Member
- Local time
- Today, 09:36
- Joined
- Mar 31, 2020
- Messages
- 82
We have a database with two tables that currently have an attachments field. My boss adores it and feels it is super easy and convenient, but I realize now that it is a problem I never should have created and that size will someday become a problem (The table after 3 years of use is 260,000 kb right now).
I am unsure how to go about fixing this issue. The consensus seems to be to use a text field with a file path instead. So my thinking is to create the new field in the table and then go through and manually enter the file path names and then delete the attachments from the attachment field after. Is this the right way of thinking? And I read that hyperlinks are "bad" and unmaintainable, but I don't understand how a file path is any different than a hyperlink except for one you copy and paste into explorer and the other you ctrl+click to open automatically? Or am I missing something?
Am I going about this the right way or is there another better/easier/more sustainable in the future idea I haven't considered?
Thank you as always.
I am unsure how to go about fixing this issue. The consensus seems to be to use a text field with a file path instead. So my thinking is to create the new field in the table and then go through and manually enter the file path names and then delete the attachments from the attachment field after. Is this the right way of thinking? And I read that hyperlinks are "bad" and unmaintainable, but I don't understand how a file path is any different than a hyperlink except for one you copy and paste into explorer and the other you ctrl+click to open automatically? Or am I missing something?
Am I going about this the right way or is there another better/easier/more sustainable in the future idea I haven't considered?
Thank you as always.