Re: TwainPage() event not firing

Options

View

Last

Unread

Previous Topic Next Topic

This topic and its replies were posted before the current version of LEADTOOLS was released and may no longer be applicable.

#1 Posted : Thursday, May 1, 2008 7:26:30 AM(UTC)

joeb

Groups: Registered
Posts: 5

I am using leadtools 13.0 in a VFP 9 application to scan a muti page document.

EnableTwainEvent is set to true

when I run the TwainAcquire method it scans in the document in but never triggers the Twainpage event to fire. If I manually execute TwainPage() after the TwainAcquire() call only the last page gets saved.

This works fine in VFP 6.

The scanner being used is a Xerox DocuMate 510.

Thank you


	Try the latest version of LEADTOOLS for free for 60 days by downloading the evaluation: https://www.leadtools.com/downloads Wanna join the discussion? Login to your LEADTOOLS Support account or Register a new forum account.

#2 Posted : Thursday, May 1, 2008 12:17:19 PM(UTC)

Travis

Groups: Registered, Tech Support
Posts: 207

Was thanked: 3 time(s) in 3 post(s)

The simple fact that our control works fine in VFP 6 and not in VFP 9 would lead me to believe the issue lies in VFP 9. I know this control also works in VB 6.0, VC 6.0, .NET compilers, and Borland compilers. So that further leads me to believe the issue lies in VFP 9.
However, before ruling out LEADTOOLS, I would suggest updating your tool kit to latest patch from our support site. You can get the patch from our support site under SDK patches. Browse to www.leadtools.com | Support | Patches.

If this does not resolve the issue, I would advise downloading our latest evaluation to see if this works with VFP 9.

Travis Montgomery
Senior Sales Engineer

#3 Posted : Thursday, May 1, 2008 12:46:13 PM(UTC)

joeb

Groups: Registered
Posts: 5

Thanks for your response Travis. I'll try that.

I've already updated the Twain driver for this scanner and tried the program on a different scanner (Cannon) all to no avail. This leads me to your conclusion.

#4 Posted : Friday, May 2, 2008 12:02:38 PM(UTC)

joeb

Groups: Registered
Posts: 5

Just an update on my status. I finally got it to work!

To ensure all ActiveX control events are processed, set the AutoYield property of the Visual FoxPro Application object to false (.F.).

So setting:

application.AutoYield = .f.

made it work like a charm. Pass me a beer.

You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.