scanning documents (1 Viewer)

  • Thread starter Thread starter Deleted member 182889
  • Start date Start date
Many years ago, when the office environment was transitioning from paper to digital, I used to allow users to scan directly from within Access - copy the file to a storage location and then store the path to the file Access. As time passed, I found that the overwhelming majority of items looking to be stored were already digitized (email attachments, local files, web documents, etc.) and I changed my design to allow users to drag and drop any file onto a form in Access and then move the file accordingly and store it's path in Access.
 
Many years ago, when the office environment was transitioning from paper to digital, I used to allow users to scan directly from within Access - copy the file to a storage location and then store the path to the file Access. As time passed, I found that the overwhelming majority of items looking to be stored were already digitized (email attachments, local files, web documents, etc.) and I changed my design to allow users to drag and drop any file onto a form in Access and then move the file accordingly and store it's path in Access.

Sounds reasonable to me. And fairly efficient.
 
My my. Two sentences. We are progressing. :)
You were given code in the first reply to do that? Have you even looked at it?
If so, do you have questions about it?
 
That's what I want. An example database so I can implement it and adjust it to my database.

You have been given samples and yet still stay with the mantra of "samples, samples, samples." Each of us offers according to our style. A few of us might have something complete lying around, but don't expect us to do the bulk of your work for you. You are asking for us to act as contract coders, which I am not. And for no pay! We still know very little about your project and its actual needs. It appears that you just hink people will toss completed, tested code your way. That is an unreasonable expectation. Anything we have lying around is probably part of a much bigger project unless we happened to be professional educators who build sample code for teaching purposes. You've got low odds on that.

Add to that the implied insult of cross-posting and it is a good way for us to decide to abandon you. When you post on another forum (cross-post) without revealing it, that means we won't know if you found your answer elsewhere - which in turn means that we might work on your response only to find that we wasted our time because you already had an answer from another source. We do what we do as volunteers - totally unpaid - who are "paying forward" the help we got when we were new to Access and got help here. When you do an unannounced cross-post you are saying that our time isn't valuable.

I'm being a little rough on you because you show a lack of appreciation for what this forum IS - and what it ISN'T. Note, however, that I remain civil in my comments. Other members are also starting to see your style. You need to adjust your expectations. Then you would get more productive answers.
 
I am attaching a module using Microsoft Windows Image Acquisition Library v2.0 to do the scanning.

The commented out enum(s) can be removed.

modUtility.Logger in LogError can be replace with your logger or debug.pring

pai1_Msg_Box can be replaced with the standard msgBox function.
Ron, this is missing?
1756650291437.png
 
Did Dvorak delete themself, or have they been banished?
He didn't do anything to warrant banishment, even temporarily. On top of his wanting us to create his project without any actual specs, it seems that he is a snowflake. At least he withdrew rather than hanging around for years and annoying us.
 
Did Dvorak delete themself, or have they been banished?
Think he just moved on to that other forum.
Noone was prepared to give him fully working code, and he wouldn't work with what had been offered. Will be interesting to see how he gets on at the other site.
 
I pulled some code out of an existing modules, leaving in some constants and enum.

modUtility.Logger is a logger function, can be replaced with debug.print or your own.
pai1_Msg_Box is a function to display a custom message, can be replace with the built-in MsgBox using the same parameters.
SystemErrorEnum.IgnoreError is an external error code that can be replaced with any long
sNZ is an extension of NZ but always returns a string, vbNullString if null

I have been using this function for a very long time, It handles connected scanners and cameras and network devices if you have the driver installed.
 
It seems the original poster has left the forum and is trying his luck elsewhere. See HERE.
I wouldn't waste any more time on this question.
 

Users who are viewing this thread

Back
Top Bottom