The latest technical response from Scanco as of 7:30 AM EDT:
They are investigating using 64 bit ODBC to determine the performance improvement over 32 bit. They created a 64 bit version of the ConnectIt service, and first tested it with the 64 bit driver that comes with Sage 100. 64 bit service with 64 bit ODBC driver does perform better on 64 bit server: it needs less memory and it manages memory better overall. It is a read-only driver, so they needed to test it with the 64 bit driver from PVX. The result of that test is that the driver keeps crashing, so they are working with PVX to resolve that.
Scanco is convinced that the root cause is IO (slow access to the MAS90 directory) that causes the ODBC queue to grow. Going 64 bit will help with the queue when ODBC does have access, but when IO is slowing down, it would be out of Scanco's control. They cannot do much if the hard drives do not respond fast enough.
Scanco has asked if we can upgrade to Sage 100 Premium, and I commented that I assumed this would take the ODBC factor out. They agreed saying that by using SQL Server they would not be constrained by the limitations of ProvideX ODBC. This option is an issue at this point, since this customer uses WO/MRP. (Not my choice, of course. We inherited this.)
It would be a large investment to convert to a production system that runs under SQL (i.e. JobOps) and to upgrade to premium, just to get the scanning to run properly. This is not what Sage 100 users and consultants have been required to do in the past to continue with the ProvideX versions. If Sage decides that SQL is the only option going forward due to the complexity of current technology and third party software, then I may accept that and deal with it. I actually would prefer that, but it cuts out the smaller users who cannot afford that investment.
That is not the case, and I have heard no mention from Sage of that ever happening. In this case, however, this is an OEM vendor asking us to do this. This is a 15-user scanning system, which Scanco admits is one of their larger systems. Perhaps the issue is that when we have larger user counts, Premium is recommended/required. I understand that, but no one determined that up front.