[AccessD] Scanning into mdb

Just another thought.
If you are scanning to Tiff format which is really the only archival 
acceptable format
aside from DJVU. You could then move the Tiff file into a pdf file and 
password protect
via ADOBE's API. ADOBE's encryption is stronger than Access. But Tiff 
files are large
2 Meg average. DJVU stores the text and background separately so is 
about 90% smaller.
but I don't know about encryption on this format. DJVU is being used by 
University libraries
for archival storage.

Or you can use encryption on specific directories in WinXP. But you 
better understand recovery problems, on disk or hardware failure ,they 
maybe specific to machine and disk type. This might
be the best method to keep out the first two groups as per list below. 
It might be the simplest to implement. Just store your image files in an 
encrypted directory. But even so if the laptop is stolen
you just crack the Access password or mdw and look at the files through 
Access.

It all depends on who you  want to keep out of the files , a browsing 
secretary, a power user, a wannabe hacker, or the FBI.

In the security world any file where you can gain a physical copy, can 
be considered compromised.

Jim DeMarco wrote:

>List,
>
>I see in the archives that some of you have implemented scanning of images into your Access systems.  I'm being asked to add some imaging to an existing A97 app that runs in the field on laptops and I've got some questions.
>
>1. Did you scan into BLOB data fields or store in graphic image format?  I'd prefer to use BLOBs as we'll be scanning HIPAA protected personal health information and I don't want files on the laptops that anyone can access.  If you used BLOBs how did you tell the scanner where to store the data?
>
>2. Are BLOBs an issue in A97?  The users fear data corruption.  There will be 1-200 medical charts scanned in per day then the data is replicated back to our main db here.
>
>3. We will be moving to A2K3 within the next few months and probably Win XP (from 2000).  Will twain support in A2K3 and WinXP be an issue?  If so what can I do in our A97 app now that will prevent issues when we upgrade the mdb?  Are BLOBs an issue in A2K3?
>
>This app is for data collection only and if we do store as BLOB we will convert to graphic image for storage and retrieval here so the images would not sit in the mdb for long.
>
>TIA
>
>Jim DeMarco
>Director of Application Development
>Hudson Health Plan
>
>
>***********************************************************************************
>"This electronic message is intended to be for the use only of the named recipient, and may contain information from Hudson Health Plan (HHP) that is confidential or privileged.  If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this message is strictly prohibited.  If you have received this message in error or are not the named recipient, please notify us immediately, either by contacting the sender at the electronic mail address noted above or calling HHP at (914) 631-1611. If you are not the intended recipient, please do not forward this email to anyone, and delete and destroy all copies of this message.  Thank You".
>***********************************************************************************
>
>  
>

-- 
Marty Connelly
Victoria, B.C.
Canada