After the Windows 11 update, the user form crashes when executing a specific code.

Hi
I have a file consisting of an Excel VBA userform, and I have been using it for the last 5 years. It's working fine.

But 15 days after the Windows 11 updates, a problem arises on 01 of my laptop where the file crashes while running the code. I have checked the code and found that it closes the uppermost user form when the code reaches this line; "Workbooks("Dbase").Close".
This is another file that does not contain the userform file.

I have many codes in the userform, but wherever this line occurs, the userform crashes. I have uninstalled this Windows 11 update, but in vain. I reinstalled Windows, and that solved the issue, but now I have the same problem
with my other system. Can anyone help me with this?

One of the code is

Please Login or Register  to view this content.

.
.
.

Thread moved to the VBA section. Please review the forum guidelines regarding code tags.

Have you confirmed by uninstalling the Windows update that it is indeed the update that is at fault? I think it unlikely that it would have taken 15 days for this to happen after an update - I would have expected an immediate issue.

Please answer the question I added. Also, you probably need to attach a sample workbook.

I'm sorry if I couldn't explain clearly. Fifteen days ago, my laptop had the same issue, and I had to resolve it that day by reinstalling windows Now, after 15 days, I'm facing the same problem with my second system, which occurred after a Windows 11 update just one day ago.

And what happened after you uninstalled JUST that Windows update? Totally reinstalling Windows does not prove that the update is to blame. You are going to need to be a bit more forensic than this.

And you need to provide a workbook for testing and very clear instructions about how to recreate the crash. It is all far too vague at the moment.

Originally Posted by WAQAS79

occurred after a Windows 11 update just one day ago.

It is very unlikely that any change in Windows will cause your VBA code to start crashing. I can't say it's impossible but I have seen post hoc ergo propter hoc (Fallacy of Cause and Effect) many times. There is almost certainly something else that changed.

My first question will be whether file Dbase is actually open.

As Ali says, it will be essential to:

1. Post your file so we can try to reproduce the problem
2. Describe the specific steps needed to reproduce the problem
3. Explain what "crash" means. Does the Excel process terminate? Does it stop responding? Do you get an error message?

Originally Posted by DavesInoIno

I'm guessing it's your use of unqualified Range objects. For an interesting read that seems relevant, reconstruct the link above to see how using Range by itself can mess things up. HTH. Dave
edit: Still not allowed to post links, Google charts tushar-mehta.com/excel/vba/xl_doesn't_quit/#symtom

Sorry but your link has errors in it. I had to poke around for a while to get the right one.
http://tushar-mehta.com/excel/vba/xl..._quit/#symptom

In any case, unqualified Range objects can be a source of bugs, but it seems unlikely that they could cause a crash on trying to close a file.

That is not evident from the code you posted. Nowhere does it re-open the Dbase file. In fact, after a second look I see you close the file, then refer to a worksheet in it after it's closed. That should raise a "subscript not found" error:

Please Login or Register  to view this content.

The only way I can imagine this could possibly work is if you have a Change event for CommandButton19 and setting it to True fires the event, and that's where you re-open the file. I normally do not condone causing change events to fire from code, because it obscures what's going on.

Are you talking about an upgrade to Windows 11 from a prior version, or a maintenance release for W11?

To sum up, I see nothing in the code you showed us that could cause this problem, and no knowledge of how it could be caused by a Windows update. Without the ability to run your code in your file, we are very limited in what we can do to troubleshoot this. However, I am going to ask that you post the code for the entire UserForm module so we can look for something that you might not think is a problem.

Originally Posted by WAQAS79

I want to show you the entire code, but I'm struggling to figure out how to present it, as my codes are very complex and interconnected.

Can you focus just on the part when it crush?

Please Login or Register  to view this content.

when it passes through this line, "Workbooks("Dbase").Close". Dbase file sucessfully close, but unfortunately now this userform also close.

Please review the Forum Guidelines regarding code tags. Thanks.