using attachment field
Does using the attachment field bloat the dB like the old Ole?
We would like to store pdfs. Currently we will be storing photos but I use a software company that compresses the file so no real bloating.
My concern is the attachment field option. Or is there a better way?
Using 2013
We would like to store pdfs. Currently we will be storing photos but I use a software company that compresses the file so no real bloating.
My concern is the attachment field option. Or is there a better way?
Using 2013
You have 2 options
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
1. Storing Files using file system
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
ASKER
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.
It does seem like a better option than just the link, because we have multiple people who will now want to see the files.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Scott,
I think ur right in that it is a much simpler setup.
I think ur right in that it is a much simpler setup.
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.