<div>
<div class="content wysiwyg-content">
Can someone tell me the pros and cons of using Access's <i>Attachment</i> field type?<br />
<br />
I have a table where I'm tracking various header-type information of audit reports (e.g., overall opinion, issuance date, etc.). &nbsp;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.<br />
<br />
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.<br />
<br />
I was hoping someone could provide some input about the size/instability, as well as any other considerations I should make before using an <i>Attachment</i> field.
</div>
</div>


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.

Thoughts on Attachment field in Access?

Microsoft Access is a rapid application development (RAD) relational database tool. Access can be used for both desktop and web-based applications, and uses VBA (Visual Basic for Applications) as its coding language.