Javier,
Any data with VARBIT data type is stored in .RB4 file. Once stored,
you don't need the actual images, other than keeping them for archival
purposes. You can also unload or update VARBIT data anytime.
Having said that, there is an overhead to the size of the database, and
if you need to update the file, you'll need to use the update process,
etc., for maintenance of those images.
Depending on the nature of the project, I would recommend to also
look into storing all images in a particular directory and then use the
table information to link/read/write/display those images in Forms,
Reports and Labels.
Also, using the Custom Plug-In option in RBASE.INI file for The
Glorious R:BASE 2000 (ver 6.5++) for Windows, you can use
RBLOB.DLL to Display/Print those images without any overhead.
The upcoming In-Line Patch-3 also includes the option to display
and/or print multi-page TIFF files.
Enjoy and make sure to have fun!
Very Best Regards,
Razzak.
At 11:07 PM 9/22/2002 -0500, Javier Valencia wrote:
I have an application that will require access to app. 1000 photos
(could grow to 4000-5000) currently stored in JPEG format and
app.400 Kb in size (each). The options are:
- Store the pictures in a separate directory and have a table in the
database that stores the filename and path and when the photo
needs to be displayed, it simply launches the photo using a an
external viewing software (such as photo editor)
- Load the picture as a blob, store it in the database and display
it from (or within) a form.
- Store the photos in a separate database, attach it to the main
database for access and display.
What is the compression/overhead when storing pictures as blobs?
The database is currently app. 60 Mb and it would grow considerably
if the photos are stored in the database. What would be the performance
penalty?
Any thought on these approaches or any other that some one has
successfully used would be greatly appreciated.
