• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 422
  • Last Modified:

Thoughts on Attachment field in Access?

Can someone tell me the pros and cons of using Access's Attachment field type?

I have a table where I'm tracking various header-type information of audit reports (e.g., overall opinion, issuance date, etc.).  We keep the reports on a shared drive (on which the database also resides), but I thought attaching the PDFs directly in the database would be nice.

I realize the database would grow that much more with the attachments. Each report is about 120KB, and we issue about 50 reports each calendar - so about 6,000KB of growth annually. I'm wondering about size at which an Access database becomes unstable.

I was hoping someone could provide some input about the size/instability, as well as any other considerations I should make before using an Attachment field.
0
songwritingcpa
Asked:
songwritingcpa
1 Solution
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
<<I'm wondering about size at which an Access database becomes unstable.>>

 Size is not an issue.   Access DB's can go up to 4GB in size and will work fine at that size.

<<I was hoping someone could provide some input about the size/instability, as well as any other considerations I should make before using an Attachment field. >>

  Attachment fields are easy to use, but most developers don't use them because they are only available in Access.   If you upsize to SQL Server, you need to extract all the data and handle them a different way, such as keeping a pointer to the file in a table, and then loading the document as needed within the app.

Jim.
0

Featured Post

The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now