>>Considerable effort was put into troubleshooting this issue on affected machines, without success.
>>
>>The final resolution was to replace Excel automation with the use of Greg Green's VFPx class:
https://github.com/ggreen86/XLXS-Workbook-Class .
>>
>>My gut feel is the future will see increasing restrictions/lockdowns on inter-process communications, function calls, automation etc both by Windows and by security/AV programs. My recommendation would be to eliminate Excel automation where feasible and replace it with this class.
>
>For intermediate tasks there is the flip side of having a non-internet visible/connected VM running XP and COM-working older versions.
>Middle finger to MS for a couple of years, until versionitis makes such an aproach more work than other ways circumventing new MS efforts.
>I do remember periods where new versions enabled developers...
That approach is fine for individual power users but can't be rolled out to a customer base.
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up
