One thing to keep in mind, though.. My Boston client has signature files that they capture and in the table we just keep a link to a file on the disk.
HOWEVER, this is a very busy client, with thousands of files generated each month. We had all the files in just one directory, and as it grew it took way too long to do a chkfile, slow to display the signatures on a report, etc... What we did was have a root directory, and then subdirectories with the year/month, such as 201203. In the rbase.dat file, it looks at today's date and creates the subdirectory if needed. Because of this we have to store the exact link in the table so we know which subdirectory it's in. This makes it not so easy to find a particular item when looking through the windows explorer. Karen -----Original Message----- From: Mike Byerley <[email protected]> To: RBASE-L Mailing List <[email protected]> Sent: Thu, Feb 28, 2013 8:38 am Subject: [RBASE-L] - Re: RB4 FILE Those dirs I set the attribute to "Hidden". You will still be able to programmatically access them. If you need further security, then you can set the ACL on the directory as needed to further protect the data. You should be able to make a directory conform to your needs. ----- Original Message ----- From: "Albert Berry" <[email protected]> To: "RBASE-L Mailing List" <[email protected]> Sent: Thursday, February 28, 2013 12:18 AM Subject: [RBASE-L] - Re: RB4 FILE : Many on this list keep a directory for bmps and so forth, keeping the : file name and directory information in the database rather than the : files themselves. Of course, this means that a file could "go missing" : without warning. Mr. Murphy suggests this will only be for the one file : you need rather than the zillion others. : : Using a 64 bit database makes it easier to keep all these pictures : accessible. The file size limits are quite large. : : Albert : : On 27/02/2013 9:53 PM, TOM HART wrote: : > That explains because this one database I started capturing and saving : > a digital signature as a varbit. I noticed that each signature has : > about 20-30 KB of data. Should I use a different data type that uses : > less data? This database could get very large quickly because I might : > capture 20-40 signatures per day. : > Tom Hart : > : :
