Yielding to others while macro is running?

I have a project in which I build some kind of a loop that takes entry from user to update information on a database. At the end of each loop it will loop back to a userforms waiting for another item designation. It just sits there waiting until confirmation event to happen then it darts out of the barn again. The problem I am facing is that no matter how uneventful of that wait for entry, the macro is still considered to be in running state. I could not open any other excel workbooks at all. It will just block up any other excel processes.

Is that any way around this design? I could let the user exit from the loop but the person will have to login again. If (s)he has to do lots of entries in a day while viewing other worksheets and excel documents in between it will be so tedious to log out and log in all the time.

Maybe instead of a userform have a worksheet with the buttons/entry boxes that you need and use that to call the macro.

In essence, the macro runs, then hides all sheet except the "userform sheet" at which point the macro finished and the user regains control of excel. Once a button is pressed on the userform sheet, the macro runs again, or a cancel could hide the userform sheet and return the workbook to normal?

Edit: Winon's suggestion may also work, code would be:

Please Login or Register  to view this content.

it won't work. In fact, my userform is shown in modal-less form in implementation. In fact, I could even go on to my target worksheet to hightlight any cell in it while having my form displayed in the front. it is fine within the same excel application. I cannot click on any other excel workbooks and try to open them while this macro is in running state. They will all be blocked. Could an excel application be made to yield to another application and having all its states saved in doing so?

I think the problem goes back to the fact that Excel inherently is not a multithreaded program.

There is another constraint built in that forces me to adopt the way I am doing things right now. As long as the macro is active it will keep server aware of my presence to enable all HTTP accesses while the program is active. If at any point, the program is done for, somehow that knowledge is lost. I try to search for a cookie file but it does not seem to be around. I am not sure how the server knows me after I log in once. All subsequent HTTP calls are all good. But as soon as I finish the macro that information is lost.

Just to make a comment here that I have found my way out.

What I understand so far that I could just as well open another excel doc by pressing shift while clicking an excel application to open another completely independent instance of excel application. This way it will not interfere with the first instance of the app where my macro is executing. But just clicking on an excel doc shortcut on my desktop in fact will go back to my original instance in which my macro is running and by default excel will block it. I think it is designed to protect a single thread application.