Toccata
That's quite a lot to ask for. Having a quick google around, there are a couple of OCX's to add scanning capabilities to an application. However, they most certainly are not free and don't come with source code.
If you are famililar with programming the TWAIN standard for image aquisition from scanners/digital cameras/webcams etc, you could write your own and probably sell it.
Access includes facilities for emailing from within itself with the DoCmd.SendObject command (look this up in help) and faxing from software is treated as a printer under most packages I have used.
As for the archiving, I would consider either storing it within an Access database, or automating one of the many document archiving packages available.
I'm sorry to not be much more help, but this is about as much as I can go on this standard.
Windows has had scanning/imaging OCX controls since Windows 95. The current controls (2000 and above) are Kodak imaging (used to be Wang imaging). See imgadmin.ocx, imgscan.ocx, imgedit.ocx & imgthumb.ocx in your System directory. The scanning control will work with any TWAIN-compliant scanner. Unfortunately, the help file imgocxd.hlp seems to be missing from my system. (Quick search on Microsoft site says help files included in Win98 & ME disks). They are not too difficult to get to grips with though - I have used them on several occasions.
Thank you. I have pretty much reached the same conclusions. Step 1 will be to write a browsing routine to search for scanned documents (.jpg and .bmp) and store the path and linking data in an archive locator table.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.