This Tuesday! Learn key insights about modern cyber protection services & gain practical strategies to skyrocket business:
- What it takes to build a cloud service portfolio
- How to determine which services will help your unique business grow
- Various use-cases and examples
eztwain driver crashes msaccess when trying to access scanner in vba
savin 4018 network twain driver.
I'm trying to scan in vba using eztwain.
with eztwerp (eztwain.dll) it opens and scans fine, but when i try to access the scanner using the dll in vba it crashes.
I'm trying to scan in vba using eztwain.
with eztwerp (eztwain.dll) it opens and scans fine, but when i try to access the scanner using the dll in vba it crashes.
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
You may need an ActiveX control for this.
Some are free, but I have used the cheap csXImage control:
http://www.chestysoft.com/ximage/default.asp
A link to an Access demo is located somewhere down that page. It will get you going.
When I worked with it some years ago, I learned that Twain drivers are animals of their own and - because of this - the support from Simon (the developer who knows just about everything about scanners) is a very big help.
/gustav
Some are free, but I have used the cheap csXImage control:
http://www.chestysoft.com/ximage/default.asp
A link to an Access demo is located somewhere down that page. It will get you going.
When I worked with it some years ago, I learned that Twain drivers are animals of their own and - because of this - the support from Simon (the developer who knows just about everything about scanners) is a very big help.
/gustav
i actually bought the csXImage control - and it crashes the same. everything works until you try to scan. you can select the twain source, you can check if its connected, but when you try to acquire image it crashes up...
When I use the ezTwerp program that comes with the eztwain.dll it works fine - perfect, but when i try to scan using the ocx or the dll it crashes..
I worked on this for hours and hours, was hoping there was someone out there that would know what im missing..
When I use the ezTwerp program that comes with the eztwain.dll it works fine - perfect, but when i try to scan using the ocx or the dll it crashes..
I worked on this for hours and hours, was hoping there was someone out there that would know what im missing..
Very well.
Then, I guess, it is an issue with the scanner driver itself.
Did you address Simon about this particular scanner? In general, drivers from manufacturers are of "uneven" quality and manufacturers' support know next to nothing about implementation of their hardware.
/gustav
Then, I guess, it is an issue with the scanner driver itself.
Did you address Simon about this particular scanner? In general, drivers from manufacturers are of "uneven" quality and manufacturers' support know next to nothing about implementation of their hardware.
/gustav
You might also want to try running Windows update to see if the newer dlls for Windows and office work better with this driver.
no. there is a program eztwerp which is 40k and it works fine. i know that the dll should worrrk. every time i access it in access it crashed. there must be something im missing.. i need this to work.
But what are the comments from the manufacturer about their appearently buggy driver?
Perhaps it will only run under an old Windows version?
/gustav
Perhaps it will only run under an old Windows version?
/gustav
i just tried twainCom demo version and it also worked. Im not sure what the limitation is. If i bought the chestysoft already - i would want it to work as well.. im not sure when this demo will expire.. it must be something simple that im missing..
If you refer to TwainCommander:
http://www.jse.de/products.html#twaincommander2
the reason why it does not cause a crash, may be that it as a command line tool runs in another process not controlled by Access.
Anyway, thanks for the feedback.
/gustav
http://www.jse.de/products.html#twaincommander2
the reason why it does not cause a crash, may be that it as a command line tool runs in another process not controlled by Access.
Anyway, thanks for the feedback.
/gustav
Premium Content
You need an Expert Office subscription to comment.Start Free Trial