Javier,
 
Our company has just started a signature capture system that works by saving the signatures as BMP files in a separate networked drive (they are stored on a NAS server) In RBase we simply have a table that stores the path for the file and links it to the documents that were signed for.  When we need to pull one up either on the screen or printer, we simply find the filename and then we can load it into the report or form by using the following code before launching the report/form 
 
SELECT Signature INTO VFILENAME IND VI1 FROM BLADING WHE BLNO = .VBLTEST
SET VAR VFILENAME = ("S:\"+.VFILENAME)
SET VAR VCOMMAND = ("SET VAR VIMAGE = ["+""""+.VFILENAME+""""+"]")
SET VAR VIMAGE LONG VARBIT = NULL
&VCOMMAND
 
So far this has worked perfectly..  Our company stores on average 1000 signatures a day., each file is exactly 3.9 KB.. we have to store them for 1 year before we can archive them and we project we will have 250,000 Signatures to actively store, which is why we bought 2 Iomega 1.8 GB NAS machines (Highly reccomended product if you need extra storage btw !)
 
If you need more information feel free to contact me.
 
-- Frank Conroy -- Systems Network Administrator
-- F.J. O'Hara Corp. -- Boston, MA
-- [EMAIL PROTECTED]    617-790-3093

-----Original Message-----
From: Javier Valencia [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 23, 2002 12:08 AM
To: List RBASE
Subject: Storing pictures

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.

 

Javier Valencia, PE

President

Valencia Technology Group, L.L.C.

14315 S. Twilight Ln., Suite #14

Olathe, KS  66062-4571

(913)829-0888

(913)649-2904 FAX

 

Reply via email to