> Any one got any other ideas on this? Other ideas? How about: don't do that?
> All I want to do is read a PDF file, > insert the data into the database and then be able to query the database and > output the pdf again either to the browser for download or to write it to > the file system again. Why not keep the files in the filesystem in the first place? Filesystems are specifically designed to handle files; relational databases, not so much. You'll have the overhead of getting the file into the DB in the first place, then if your database isn't the latest & greatest you'll have to do special maintenance when you delete the record. Can your DB handle unlimited size blobs, btw? If it's just a matter of not having the file in the location they were created you could always <cffile action='move'..> them around on the drive. But if you really need to, and blobbing doesn't work, check out binary to hex encoders/decoders such as CFX_HEX, and stuff the data into a long character field. Paul Haddon Technical Services Manager Formstar Print Technologies --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~----------~----~----~----~------~----~------~--~---
