[FX.php List] Re: Container Quandary

[Bob Patin]

>
> I wanted to store the files in the database container for  
> organizational purposes so that record data, pdf, and mp3s are kept  
> together.  However if you say it's not a good idea, maybe I should  
> rethink it.  On the upside, this site would not have much traffic -  
> maybe one user upload per week with a limited download access.

Here's how I do that: when someone wants to upload, they click a link  
(or a button); this sends that record's recordID to the next page.

On the 2nd page, they select the file to upload; the file is uploaded  
to the web server, and the filename is written into a variable. It  
also puts a timestamp in front of the name, to prevent users from  
accidentally overwriting files.

Then, it takes that filename and writes it to the FileMaker database's  
record, editing the record using the RECID that I captured in the  
first step.

That way, each upload is associated with a specific record in the  
database.

Hope that helps,

Bob Patin



Longterm Solutions
bob at longtermsolutions.com
615-333-6858
http://www.longtermsolutions.com
iChat: bobpatin
FileMaker 10 Certified Developer
Member of FileMaker Business Alliance and FileMaker TechNet
--------------------------
FileMaker hosting and consulting for all versions of FileMaker
PHP • Full email services • Free DNS hosting • Colocation • Consulting


>
> I have used FileMaker in the past to store many large PDFs with a  
> reverse approach where the database acted as a file & content  
> manager which then generated static HTML files and uploaded both  
> PDFs and static HTML to webserver via FTPit.  It is still working  
> well and the client loves it since it's saving him thousands in web  
> developer costs per year.  Because it seemed to store PDFs in the  
> desktop app well, I figured why not use it for web server storage  
> too?  Hummm....
>
> David Cox

-------------- next part --------------
Skipped content of type multipart/related