5 hours ago: Our file storage provider is running maintenance today. If any videos don't load, wait a minute, refresh the page, and try again. Sorry for any inconvenience.  Dismiss
Free Lessons
Fast Tips
Topic Index
Home   Courses   Index   Templates   Seminars   TechHelp   Forums   Help   Contact   Join   Order   Logon  
Back to Evil Access Stuff    Comments List
One Reason to Store Attachment Upload Images   Link   Email  
Kevin Yip       
2 years ago
External files are susceptible to file name changes, relocations, deletions, path name changes, relocations, etc., and other mishaps.  These can be avoided by storing files in an attachment field of an Access table.  If I needed a more fool-proof way to prevent tampering of the files, I would definitely consider storing them in attachment fields.
Alex Hedley              
2 years ago
Just lock down the permissions of the folder(s)
Kevin Yip       
2 years ago
As long as one user has full permission, which is always the case, mishaps are always possible.  Sometimes you not only need to protect data from other users, but also from yourself.
Alex Hedley              
2 years ago
But then on that logic wouldn't they be able to harm the attachment fields too?
Need a better reason than that to use it.
Kevin Yip       
2 years ago
But there are much fewer available ways to tamper with the attachment fields than ways to tamper with Windows files, because Windows makes everything easier to get to.  Mistakes are less likely to happen if files are harder to get to.
Alex Hedley              
2 years ago
Take the time to lock down the file share with correct permissions
Kevin Yip       
2 years ago
As I said, there is always at least one user with full permissions to Windows folders.  Windows also puts file shortcuts on the taskbar, Explorer, recent document list, etc.  That's what I meant by Windows making it easier for you to access files.  With Access attachment fields, the only way to get to the files is if you remember the exact database, table, attachment field name, etc.  Having said that, I've never used attachment fields myself because of the reasons Richard mentioned regarding the cumbersome handling of attachment fields.  But I'm definitely putting it in my back pocket in case I have a future need for it.
Alex Hedley              
2 years ago
Mute argument, that same user would have the same full permissions to your database.
Windows allows you to make it as easy or as hard as you want to access the files, in the same way you'd write code to allow your users to do things in your db.
You'd have to know the exact location of the file in windows.
Laughable that you don't use them but think you might have a need for them?
Kevin Yip       
2 years ago
"Same full permissions" doesn't mean the same ease to accessing files, which is my point.  If full permission to Windows takes you N steps to open a file, then full permission to an Access DB takes you N+10 steps to open a file inside an attachment field.  Richard put it on the evil list precisely because of its cumbersome usage.  And no, you don't need to know the exact Windows file locations because, as I said, Windows puts file shortcuts everywhere to convenience you.  Windows has tons of "quality of life" conveniences that make accessing things easier, and that's my whole point that I don't know why you aren't accepting.
Alex Hedley              
2 years ago
Or in Access could also take you N steps as well
Maybe re read the reasons not to use it then it might sink in why you shouldn't.
Kevin Yip       
2 years ago
These are such microscopically minute issues we are debating on.  Let this sink in for you instead: if an argument lasts more than 10 minutes, then BOTH sides are wrong.  Attachment fields are useful to some, useless to others, as it has both good and bad points (as do all things in life), and THAT is the truth. See how easy it is to settle this?
Dan Jackson              
2 years ago
Disagree. If you have a form with an "Upload" button which copies a file to a hidden directory in the same root as the database, there would be no more risk of human error than using the attachment option.

For example, suppose you have a catalogue page and you want to upload an image to the page. Instead of linking to the image you have, get the button to COPY the image into a hidden folder where the database is stored (Maybe alongside your backend if using Split DB) and link to that.

This thread is now CLOSED. If you wish to comment, start a NEW discussion in Evil Access Stuff.


The following is a paid advertisement
Computer Learning Zone is not responsible for any content shown or offers made by these ads.

Access - index
Excel - index
Word - index
Windows - index
PowerPoint - index
Photoshop - index
Visual Basic - index
ASP - index
My Account
My Courses
Lost Password
Student Databases
Change Email
Latest News
New Releases
User Forums
Topic Glossary
Tips & Tricks
Search The Site
Code Vault
Collapse Menus
Customer Support
Web Site Tour
Consulting Services
Affiliate Program
Richard Rost
Free Lessons
Mailing List
Video Tutorials
Learning Connection
Idiot's Guide to Excel
Volume Discounts
Payment Info
Terms of Sale
Contact Info
Support Policy
Mailing Address
Phone Number
Fax Number
Course Survey
Email Richard
[email protected]
Blog RSS Feed    YouTube Channel

Copyright 2024 by Computer Learning Zone, Amicron, and Richard Rost. All Rights Reserved. Current Time: 7/14/2024 11:33:49 AM. PLT: 1s