Hello,
I'm working on a scientific database which contains some massive microscope image files - and I mean upwards of 30 megabytes in TIF, not even in BMP. Obviously, I don't want to attach them directly into my database as an OLE object or whatnot because of the shear size and time it would take them to load. Once the images are in a windows file folder, they'll never leave it, and their location relative to the main database will always be the same.
My idea is to add an unbound image and set its route to the file location on a hard drive. The file location would change from record to record, hence the photo location would essentially be what users would enter in and would have its own field in the table, while the form would display a small version of the picture by calling the photo location.
Has anything like this been done before? Are there better ideas for managing huge files?