I found a way to do this using Task Scheduler.  Without using the search index, there are several problems with Sage 100 2020 PU3 lookups. 

Is there a work-around for this, or is it best practices to use the search index going forward?

I'm still experiencing problems with lookups after installing Sage 100 2020 PU3.  For clients that have never ran the build search index utility, the lookups are not working correctly.  Also, when typing in a G/L account number, a customer number, etc., the response time to retrieve the record is 6-10 seconds.  The only work-around I have found is to run the build search index utility.

This problem has happened on all of the Sage 100 2020 PU3 installations.

I need a work-around for this problem.  This is critical for non-cloud clients because I believe the build search index utility is a cloud-only feature.

Try disabling Auto-Complete in user maintenance.

Thanks for the suggestion, but all of our clients like the auto-complete feature.  

Agreed, but if the Advanced search is not an option, some users may prefer to turn it off (and type a partial value then F2 for the filtered lookup) instead of the long delay typing.

I heard rumors of pre-release code as a fix (before the next  PU), if the customer is willing to sign a waiver.  Contact Sage to confirm what your options are for something like that.

BShockley & Kevin M - We are working on a hotfix for this slow type ahead issue.  Stay tuned.

Dang if you do, dang if you don't....  I like to stay on top of PU's by installing ASAP.  So I am behind the eight ball on this.  For those clients with the latest PU installed, they are not happy with the delay, but they like their auto complete.  Not a fan of advanced search (from the get go), last I used it, ONLY 10 records are returned even though their could be 20 or more that fit the criteria.  So I have stopped doing PU installs and hesitate to do ANY migrations right now.  Not a good place to be in...

I'm going to agree on that point 100%.  Perpetual customers paid a big buy-in cost initially (not paid by subscription customers), and the perpetual customers get fewer features?  Backwards logic.

The perpetual customers spent a lot of money with Master Developers for features Sage didn't provide. I would say that makes them a long term loyal customer.

The subscription customer gets in the door renting the software and is less likely to make source code investments when Sage offers a supported open scripting option.

Don't penalize those not willing to buy the software again on a subscription and keep the original promise of how Sage treats their customers and does business.

I'm sure the Sage 100 development team would prefer maintaining and enhancing one code base for the three versions Sage is already offering. (Standard, Advanced and Premium)