Re: What DB to use for lots of IMAGE files?

kpijnenb@xs4all.nl (Kees Pijnenburg) wrote: >tpcarmen@NO_EMAIL_SPAM.SEE_SIGNATURE_FOR_ADDRESS.org (Terry >Carmen) wrote: > >>In any event, although it's possible to store large files in a >>database, I've had much better performance by storing the image with >>the native underlying filesystem, and only storing the image path and >>filename in the database. > >>Using one of the keys as part of the path name will allow you to limit >>the number of images in a single directory to an optimum number for >>the filesystem. > >>For example, under NT, a maximum of a few hundred files per directory >>seems to be optimum, so one system I wrote stores the files as: > >>\\\\servername\\images\\<year>\\<month>\\<day>\\<first 4 digits of image >>ID>\\<imageID.TIF> > >Although I fully agree with your setup, I was wondering about the >implementation of the security. Do you have any ideas if it is >possible to limit access based on rights to the database. > >As an example assume a table containing usernames and picture >names to indicate whether or not a user has access (I know, a >lousy setup for maintenance). Now it would be nice if each user >could only see the files he/she has been granted access to. And >preferably without changing network security for each file (and >each time something in the rights table of the database changes). > >Any ideas??? > > >Kees Pijnenburg - P.O. Box 84 5374 ZG Schayk The Netherlands > kpijnenb@xs4all.nl > I have a system like this. It is a document management system (a client/server type) where a stand-alone machine is placed on the network and simply looks for requests based on a database everyone has access to on the file server. The file names are in the file-server's database and also a security level required to view the document. While this can be overcome by someone with a raw dbase package, it works well for me here. The user only sees the file names of the images he has access to. I believe I used the SET FILTER with a macro substitution for the security level (but I'd have to look - the program is old and it took a while to get that part working correctly).