Not that we've seen. The biggest issue is that it locks you into using Access, since other database engines (like SQL Server) don't recognize the Attachment field. Plus, it's difficult to work with from a code standpoint, and it can make reporting a challenge (if you must include the attachments in a report).
IMO, you're better off storing your PDF files somewhere and store the link to the PDF file. If you have multiple items that will be associated with a single record, you can use a one-to-many link table to store those relationships.
As mentioned above you will only store the path of the file .
2. Use of Document Database
With some effort you could use a Document Database like from FireBird and store all your files on a single Database file with no size limitations...
The process goes like this (I will use the Firebird for this example)
You create a DSN connection to the server
You create a ADODB.Stream
You connect to the Server
You upload the file to the server using the stream
Trying to look into Firebird...got it setup (Firebird that is), but not sure how to get that connected to my current dB to upload to firebird db? I tried connecting using Access odbc connection but jt fails. Sees the table but doesn't connect. So still working on it.
It does seem like a better option than just the link, because we have multiple people who will now want to see the files.
I think ur right in that it is a much simpler setup.
Microsoft 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.
IMO, you're better off storing your PDF files somewhere and store the link to the PDF file. If you have multiple items that will be associated with a single record, you can use a one-to-many link table to store those relationships.