Hello,I am the person that will be helping you today. Before we begin, please, understand that responding to my questions does not cost more. Also, me responding does not cost more.May I ask for you to upload one of the documents or an example of one that you are having issues with? I have looked at your code. I don't see why it would work slow, as you stated it does. You may upload the file to this page by clicking the Send files button.I will be standing by, looking forward to your response.Thank you,Jason
Thank you for the information. I am sorry, but I will not be able to help this time.
For this reason, I am opting out of the question and allowing another expert the chance to help.
The next expert will see all that is on this page, so there will be no need to repeat anything.
When another expert picks this up, you will be notified by email.
Thank you for your patience.
Hi there, my name is***** thing you can try is to apply the protection without using a password. This will avoid the SHA1 hashing but will still keep the user from messing with the sheet unless he really wants to maliciously destroy it.
I had a similar issue and using the protection without a password ***** the problem for me, that's why I suggested it.
It sounds like you've already tried most of these kinds of workarounds without any luck. In reality, the reason for having these complications is that you're pushing the boundaries of how a spreadsheet was designed to be used. That's not a bad thing, but it tends to reveal weaknesses in an application that don't ever get tested during development, and the intent is usually to mimic functionality that's already built in to a more suitable tool. I would say the next place to look would be at code optimization. I don't know if there are opportunities there because I haven't looked at your code. But, if you're going to rewrite code, you're probably better off putting the whole thing into a database. Once you do that, all these problems go away. Please understand that the intent of my answer here is not to be critical, but to put some "big picture" context around the issue.