Still no fix for this? One of the archived forum threads suggested updating the scanner drivers... which we have done. This only happens when using capture, not when using any other scanning program, which leads me to believe this is a problem in capture.

It seems there is an "invisible" step when scanning from capture which automatically splits the document into individual tif files just like the split multipage tif step available in the workflows. If I scan a multipage document using a different program and submit it to the workflow the pages are in the correct order through out the process. It's only when i use the scan tab in Capture that this problem happens. it's creating multiple files (doctitle_0001, doctitle_0002, etc.) and if you look at these individual tif files the 0001 file is the last page of the document instead of the first. So, the bind pages step in the workflow is using this suffix to put the pages back together in the wrong order. I reiterate that this does not happen with the split multipage tif step in the workflow. The 0001 file (or actually the 0000 file) from this step is the first scanned page of the document whcih is correct.

Our workaround is just to scan the pages in reverse order, in other words, put the pages into the scanner last page first. However, we are dealing with some very large documents and over 150 boxes of them have to be scanned in. That makes it a very tedious process.