Integration of Document Imaging

Looking for some direction...

I have a database that processes information collected from several printed
documents. After they are processed, we file them in a typical file folder/
file cabinet system. I would like to integrate a document imaging system
using the barcoding within access.

I would like to print coversheets for these documents (including a barcode
tied to a specific folder on my network). Then have my users walk to the
scanner and have the docs routed to that folder automatically without
manually reindexing anything.

While I have seen several applications capable of doing imaging, I havent
seen many that I can sync with access that would direct preprinted barcodes
to a specific file path. Ideally, I do not want to reindex them. I would
rather just have access create the folder and code the barcode to link to the
newly made, or existing folder.

Does anyone have any ideas on what direction I should go? Any help would be
appreciated.

-Brad

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...esign/200904/1

Brad,

I noticed that nobody answered. There's a syneregy of two big challenges
in your quest and post:

You've not made it clear what you are specifically trying to do. In
several areas you use broad (=vague) technical terms in lieu of saying the
specifics. One term, "index" which has a specific meaning in Access / this
forum, but it's clear that you are using different meaning that conflicts
with that, but not told us what that is. In others you use vague terms (e.g.
"tied", "using the barcoding within Access". "link") in lieu of being
specific. Finally, it was pretty clear that you were initially talking about
a paper file folder / file cabinet system, it seemed later that you were
talking about electronic file folders. Not sure if you are talkign about
paper or electronic file folders or both.

To help sort through the above, I would recommend making the distinction
between the bar code itself (a graphical object) and the data which is
encoded in it / can be read from it.

The other is that, once you clarify what you're trying to do, it probably
includes automation and control of a lot of precesses outside of Access,
although Access might provide a good "hub"

Hope that helps a little.