Bill, Gunnar, Javier, Razzak, Mike, Rachel, Thanks for all of your suggestions. I will try in table and in directory locations for the PDFs just for my own education. Got the network manuals out to learn more about the related security issues and I can see how Javier's idea of putting encrypted PDFs in a secure directory will work. Simply had not thought of that before because the need had never come up and I try to avoid network issues. Sometimes you just have to learn more than you planned to get where you want to go. What a group!
Tom Frederick ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Rachael Malberg Sent: Wednesday, March 11, 2009 3:22 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Saving PDFs to Database I'm with Javier here, I tri...I mean...I heard about this person who did the whole saving documents in the DB initially and if you do a few it works beautifully but if do a bunch, like the medical supplier I'm contracted with, not so beautiful.. Back ups or reloading started taking forever!! plus had a glitch twice and even though the field showed there was data in it, it had gotten corrupted, there was a network failure, or some gremlin but there would be a group of records that wouldn't display a document in the blob viewer, tried exporting it and got errors 'unreadable file'. So I now create cryptic file names and directory structure and store all documents outside the DB (but on the server only), record the location and have had no issues. The other thing is this company just passed Medicare accreditation which is a full HIPPA/OSHA compliance review and they looked at our current application and because all of our documents are stored on a secured server, which is in a locked cabinet, it is HIPPA compliant. ~Rach ----- Original Message ----- From: Javier Valencia <mailto:[email protected]> To: RBASE-L Mailing List <mailto:[email protected]> Sent: Wednesday, March 11, 2009 12:36 PM Subject: [RBASE-L] - Re: Saving PDFs to Database In principle, I agree that the simplest way would be to store the PDF reports within an R:Base database; however, 2 issues come to mind. First, as you know, the R:Base created PDF files tend to be large and, if thousands need to be stored, it will likely exceed the 2 Gb file size limit (ask me how I know this)...of course, V8 or newer versions would not have this limitation. Second, when backing up the system, the majority of the data you are backing up is data that has gone unchanged and will not change; the storage of these large files might present a problem. When you use external files, you can do sequential backup that include only the new files. A system could be created that stores encrypted/password protected PDF files in a password protected directory that can be accessed using only valid passwords. The database would store the name and location of the file as well as the password to decrypt the file. Javier, Javier Valencia 913-915-3137 ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Bill Downall Sent: Wednesday, March 11, 2009 1:00 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Saving PDFs to Database Each provider, usually with their own lawyers and risk management people, interprets the law and decides how to implement appropriate protections. I'm with Tom. A lot fewer people are self-taught at hacking an R:BASE Grant-Revoke protected, encrypted database, than are self-taught at hacking the Windows file system. Bill On Wed, Mar 11, 2009 at 1:52 PM, MDRD <[email protected]> wrote: But the VA lost a HD with all the doctors info on it?
