How to exit VBA loop

Topic

New Reply

I have developed, in conjunction with “Zeddy”, a project that winds up as a shared workbook. It has just developed a problem where by it goes into an endless VBA loop checling for I don’t knnow what!
Is there any way I can stop the loop to turn the sharing off and access the file?

Reply | Quote

Replies

Without an idea where it’s looping it’s a bit hard to suggest.
Are you able to make it loop or does it just do it when it feels like it?

cheers, Paul

Reply | Quote

Paul
It gets into the loop on opening

Reply | Quote

If the code is still running you can force a break by pressing Ctrl-Break on the keyboard.

Failing that, you can kill off the application or process using the Task Manager

Reply | Quote

Andrew
Yes I can kill it off using Task Manager but that does not give me access to the workbook to stop the Sharing

Reply | Quote

You can step through the code in the VBA IDE (it used to be Shift F10 to open the debugger) then press F5 to step through.
Alternatively, put some messagebox followed by exit command to make the code break at some point, then let it run on it’s own.

cheers, Paul

Reply | Quote

Paul
I cannot get access to the code becsue it is a shared workbook and effectively locked

Reply | Quote

Phil

Is your question “How do I stop a macro from running automatically on opening a Workbook?” or “How do I stop a workbook from being shared?”

What is Zeddy? Is that relevant to why the workbook is shared?

Reply | Quote

Andrew
Yes, how do I stop the macrto from running automatically on opening. If I can stop it running I can stop the sharing.

“Zeddy”, Richard, is the forum member who assisted me when I designed the training record spreadsheet

Reply | Quote

You can change the security settings in the spreadsheet program to prevent macros running.

cheers, Paul

Reply | Quote

Hold the Shift key while opening the workbook.

Reply | Quote

Thanks Rory
Problem was a conflict with a misspelled staff name between the staff list and the code.

Fixed however, there appears to be a conflict between Office 2010 and Office 2013. mmmm! maybe because I converted it the 2013 format

Reply | Quote

Fixed however, there appears to be a conflict between Office 2010 and Office 2013. mmmm! maybe because I converted it the 2013 format

You’ll have to be more specific, please.

Reply | Quote

Rory
Thanks to your suggestion I managed to open the file and find the offending code and fix, but I did notice that the file when opened in 2013 was in “compatibility mode”

Reply | Quote

“Every Problem you deal with today Is, the direct result of a solution to, a previous problem !”
Werner Earhardt

Reply | Quote