Unable to execute VBA for the second time and thereafter

[alee001]

It happens in the same place every day. When I use the PAD to execute the Excel VBA button, an error occurs the second time or after that. The strange thing is that there is no problem if I execute it manually or skip the next step. What is the reason?

[Deenuji]

@alee001 

What is the specific error message? Could you please provide a translation?

Meanwhile, please refer to the following link for troubleshooting in case it's a code execution issue.

Code execution has been interrupted | Microsoft Learn

[Agnius]

Can it be that your file name changes? Which action does it fail on? What's the error message?

[Chetan_Ninghot]

Hi,

Are you execute or run VBA by clicking on this button by using click on it 

can you provide more details about your scenario.

(Note:- if you got your solution you can mark as solution and gives kudos)

Thanks & Regards

Chetan Ninghot

[alee001]

Thanks for the reply,

There is no error message because I set up to redo step 12. I can only forcefully terminate the process and then re-execute the process to pass.

[Deenuji]

@alee001 

The retry mechanism is okay, but I'm attempting to understand the specific error being thrown before the retry mechanism kicks in. Therefore, if feasible, let's temporarily disable the retry mechanism in the error handling process and capture the exact error being thrown.

Thanks,
Deenuji Loganathan 👩‍💻
Automation Evangelist 🤖
Follow me on LinkedIn 👥

-------------------------------------------------------------------------------------------------------------
If I've helped solve your query, kindly mark my response as the solution ✔ and give it a thumbs up!👍 Your feedback supports future seekers 🚀

Thanks,
Deenuji Loganathan 👩‍💻
Automation Evangelist 🤖
Follow me on LinkedIn 👥

-------------------------------------------------------------------------------------------------------------
If I've helped solve your query, kindly mark my response as the solution ✔ and give it a thumbs up!👍 Your feedback supports future seekers 🚀

[alee001]

The following is the process background,

The process is to operate 20 identical VBA files (01~20), each file has a sequence of button input settings to perform backtesting.

The problem occurs in step 20, because sometimes a file in the batch file will have an interruption error message and cannot be pressed, so you need to set a retry button to continue the process, but each process can only be completed successfully the first time, and the second or subsequent times. Problems will arise when executing the process.

The retry mechanism keeps pressing the button so no error message appears and the process can only wait or forcefully terminate the process.

There is no problem with the manual operation of the VBA button in step 20. However, the VBA error message appears when the PAD is executed.

Is this a VBA compatibility issue or a PAD bug?

[Chetan_Ninghot]

Hi,

It is not vba compatibility issue , but while running the process you have got some issue or error can you provide exact what kind of error occurs .

In your process you are clicking on button on excel for executing the vba process its may be compatible for click on button .

my suggestion for it if possible to all vba button or process code in one vba excel file , for that you can execute your all vba process by run excel macro action by using that you does not required to click on each vba button.

(Note:- if you got your solution you can mark as solution and gives kudos)

Thanks & Regards

Chetan Ninghot

[alee001]

This is not a problem with the VBA file itself, because no matter how many times you manually execute all buttons of each file, there are no VBA errors at all. Each button has its own set of codes to execute, instead of using a bunch of codes for multiple buttons.

If it is not a bug, why can the PAD process only be executed for the first time?

[alee001]

Every time I execute the process for the second time, a VBA error occurs. Each time, there are only two solutions:

1) Press End in the VBA error message, and then manually press the button on the worksheet again to continue the process.

2) Terminate the PAD process and re-execute the process.

For no apparent reason, only the first VBA button had problems executing the second process, but the other VBA buttons had no problems.

[JeffreyDSmith]

I must restart my PC each time after using PAD. Sometimes, PAD screws up my macro-enabled Excel so badly, that I have to delete it and restore from back-up copy. (I keep several back-up copies.)

[kinuasa]

Instead of using Send keys or UI automation, how about directly executing the macro using the "Run Excel macro" action?

[alee001]

My process is to operate multiple VBA file buttons that have been opened, so I can only use UI elements to operate them.

It seems that the frequent operations using UI elements in PAD are not fixed. I think it may still partially affect the VBA operation?

[kinuasa]

---

@alee001 wrote:

There is no problem with the manual operation of the VBA button in step 20. However, the VBA error message appears when the PAD is executed.

---

"Run Excel macro" action to execute a command button's click event is equivalent to manually pressing the button. Both these actions trigger the same behavior.

If there are no problems with manual operation, I believe it would be easier to directly execute the VBA macro.

[alee001]

Even if there is no problem with the manual button, I wonder why an error occurs every time the process is operated for the second time.

I know that sometimes the PAD process button operation too fast will have an impact, but I tried adding a second to wait for buffering and it didn't help.

[kinuasa]

If you can identify which part of the macro is causing the error, it could provide valuable hints for troubleshooting. However, if the macro is protected, the code won’t be visible, making it challenging to pinpoint the issue🤔

[alee001]

The macro is written by me without any protection or plug-ins.

The execution process is used four times a day for fifteen minutes each time. There may be only one day per week where the second execution process can be successfully passed.

Is this strange?

[alee001 · Accepted solution]

Because there was a bug, I added a debugging rule in the 12th step of the process. I tried to cancel this rule a few days ago and found that the VBA error was automatically solved. Now the process can be used normally even if it is executed multiple times.

I don't know the reason. Maybe the old debugging rules affect the new PAD version?