The BIG problem I am having is with Excel automation. Since 2002 my VB6 and VB.Net automation code has worked well and without fault. Back then, I followed the Microsoft guidelines for the implementation of the automation code. In the last 4 months I have
been inundated with calls from users, because the automation is failing. Microsoft have changed things and have broken backward compatibility.
My software automates Excel and populates one or more Spreadsheets in a Workbook with data. There is much copying and pasting. The automation now fails at random points in the processes, with various error messages. It did not do this before.
If anyone with some technical knowledge at Microsoft is listening ..... In my case it appears to be a 'timing' issue with the clipboard. The original code used Early Binding (as recommended). I have now changed this to Late Binding. Also, before each copy,
I have now inserted a 2 second delay. Before each paste, I have inserted a 2 second delay. When the Workbook is Saved and Closed, and when Excel Automation is Quit, I have inserted a 2 second delay. This appears to have overcome the problems I have been having.
As I say, a timing issue seems to be the problem. I know this is not related to the manual copy and paste problems that people are reporting here, but I figure it is all related. You guys at Microsoft have change some underlying mechanism, and you need to
sort it out.
It's all very well saying it is not Excel related, or Windows 10 related and that it is something to do with some 3rd party software or device, and Windows is not responsible. The 'oh, it is not our problem, it is a problem created by some 3rd party' is
not really acceptable. The operating system should be taking control and straightening out the error by whatever means.
All I can say is that Microsoft is in control of Windows, and if a device or plug in causes havoc with the clipboard (or whatever the problem is) then Microsoft should program in a graceful solution that recognizes and deals with the problem. Putting up
feeble error messages, informing the user that there is a problem, is not dealing with the problem. Simply, deal with the frigging problem.
Steve