Andy Lacey
andy at minstersystems.co.uk
Sun May 15 05:53:06 CDT 2011
I'm totally with Rocky. Andy -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin Sent: 15 May 2011 05:52 To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Should I use Attachments? I always put the path and file name in the table and leave the pdf, doc, jpg or whatever outside the db. I found that importing even the simplest graphic into an access database bloated it way beyond the size of the file being imported . Is this what you're asking? Rocky R -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Darrell Burns Sent: Saturday, May 14, 2011 5:33 PM To: 'Access Developers discussion and problem solving' Subject: [AccessD] Should I use Attachments? New subject: my client wants to link PDF documents to records in an Asset table in an A2007 app. The attachment data type is perfect for what I want to do, but I've heard bad things about it. I know one caveat is that it's not backward-compatible. I've also heard that it's a performance drag. (I tried using OLE fields in A2000 a few years ago and quickly abandoned that approach). The Asset table would range from a few hundred to a couple thousand records per client. I'll be deploying the app as a runtime. I'd be interested in hearing the pros & cons of attachments. Thanx, DB -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com