Jim DeMarco
Jdemarco at hudsonhealthplan.org
Wed Jan 4 10:29:43 CST 2006
Thanks Jim. Did you use the Kodak Imaging control to call the scanner? Jim DeMarco -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Jim Lawrence Sent: Thursday, December 29, 2005 5:06 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Scanning into mdb Hi Jim: In the application that I wrote the scanner program was called from the Access app and therefore I could hard code the profile, naming and save-path of the scanned images... similar to the feature of a full-licensed version of WinZip. I did not have to encrypt the images (jpg) as the application also moved the graphics to a secure centralized directory on the server, after the new image was saved locally. HTH Jim -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim DeMarco Sent: December 29, 2005 10:25 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Scanning into mdb Thanks Jim and Jim who replied from Jim who posted! So I gather I should save to files or encrypt the BLOBs. WinZip has some automation tools. I wonder if I should see if I can zip the images and password protect the zip file? Hmm. I asked about TWAIN support because I thought the Kodak image control was removed from XP. Doesn't that have something to do with imaging in Access? One last question. If I can scan the images can I automate the saving and naming of the files or will the user have to do that? Thanks again Jim DeMarco -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Jim Dettman Sent: Thursday, December 29, 2005 12:50 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Scanning into mdb <<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?>> Definitely want to go with a file on disk in some type of graphic format. If you let Access handle the insert, it places an OLE wrapper around the object which can double the storage required. If you really want, you can save the image to disk first, then pull into a BLOB on your own. That will avoid the bloating issue. However you'll need to export the BLOB back out to be able to do anything with it. In your case, this might be a good fit, as Access on it's own is easily crackable and I'm sure would not meet HIPPA standards. When your write/read the BLOB, you can use some form of encryption on it. Then distribute the app as a MDE so your code can't be looked at. <<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.>> I've never found memo or OLE fields to be an issue. Others have. A lot I think depends on the type of environment the app runs in and the fact that many people try to make Access do things it was never meant to do (like run over a WAN). <<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?>> I can't think of any specific issues; all the drivers will still be 32 bit and twain support has changed little if any over the years. HTH, Jim. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Jim DeMarco Sent: Thursday, December 29, 2005 10:58 AM To: AccessD (E-mail) Subject: [AccessD] Scanning into mdb 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". **************************************************************************** ******* -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com **************************************************************************** ******* "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". **************************************************************************** ******* -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com *********************************************************************************** "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". ***********************************************************************************