How do I store attachments with a MySQL backend?

[alexandervj]

I have an Access front end and backend right now, however when I made the backend I made it so that Access stores the attachments in the backend instead of a path to the backend. Now the database is growing rapidly and I need to migrate to a MySQL backend. I'm not sure how this will work with the attachments though? I definitely want to just store paths to the attachments in the MySQL database. Whats the best way to do this? Thanks

[CJ_London]

You don't normally, you store them outside and have a filepath/name to open them. They can be stored as a BLOB field type, but I've never used them - have a look at this link

https://doc.zarafa.com/7.0/Administr..._database.html

if you google 'MySQL attachments' you will find plenty of links on the subject

good luck

[alexandervj]

Thats basically what I said in my post. I need to know how to take an Access backend, with attachments stored in it, and migrate it to MySQL with attachment paths instead of actual attachments. the data is simple, just the attachments part I'm not sure about

[ItsMe]

...I need to know how to take an Access backend, with attachments stored in it, and migrate it to MySQL with attachment paths instead of actual attachments....

Then, this may be of some help.
https://www.accessforums.net/access/...tml#post237825

[ItsMe]

Thanks ItsMe, I think that might be a little more VBA than I can handle. I'm building a PHP front end and getting rid of Access and just needed a temporary solution to reduce the size of the database until I can finish the new php front end. I guess I'll just try to finish the new front end asap and make everybody use that

It is up to you. You will need intermediate VBA to manage the task. You will need to use DAO and iterations. However, a lot of the code you see in the example is to create a user interface to export and attach attachments.

[orange]

Why do you have to store the "attachments" in the database? Often, people want quick access to the attachments. They aren't necessarily concerned with where "they" are stored, or backed up etc. They just want "them" available, accessible..

[ItsMe]

Why do you have to store the "attachments" in the database? ..

I think the OP clarified they want to use the path in a text field. It is a matter of exporting the existing attachments.

[orange]

Thanks for clarifying. As I reread the posts, I think several interpretations are possible.
It seemed first that (the storing the attachment in the database) bloat was the issue. Then it seems that moving to MySQL is a goal.

Not sure which/what is the driving factor.

Always suggest/recommend you store the files on the file system, and store the link within Access. This give accessibility, availability and prevents/reduces the bloating effect.

One issue that could arise with links in the database and files on the file system is that backups of the database- do not backup the files. You need to have a plan for that.