Background:
I was wondering whether to post this to the Sharepoint or Excel board but seeing it seems to somehow be a VBA corruption, decided to go with Excel.
An excel spreadsheet with VBA code is stored in Sharepoint 365, which may or may not be part of the cause.
The problem:
Users open this to add/update entries. Every now and then, VBA errors show up, which can be cleared by logging off and logging on - a symptom indicating VBA run-time corruption in some way.
However, very occasionally, the apparent errors cannot be cleared even by logoff/ logon (nor restarting the machine). This had me stumped for a while until I tried the following steps (which to me, whilst it "fixes" problem, it is a sledgehammer approach to crack the proverbial walnut) -
The question:
What I'm looking for is where the corruption might be within their "profile". Is there a folder / file (even if marked hidden) that the logged on user can delete that will clear the apparent corruption (without an Admin doing anything ... it can take a while for an Admin to be available to do this
). The user only has std rights, not Admin.
And as a byproduct, just maybe, this area might also be a "cure" for the other Sharepoint "read-only" issue as well
I was wondering whether to post this to the Sharepoint or Excel board but seeing it seems to somehow be a VBA corruption, decided to go with Excel.
An excel spreadsheet with VBA code is stored in Sharepoint 365, which may or may not be part of the cause.
The problem:
Users open this to add/update entries. Every now and then, VBA errors show up, which can be cleared by logging off and logging on - a symptom indicating VBA run-time corruption in some way.
However, very occasionally, the apparent errors cannot be cleared even by logoff/ logon (nor restarting the machine). This had me stumped for a while until I tried the following steps (which to me, whilst it "fixes" problem, it is a sledgehammer approach to crack the proverbial walnut) -
- Have user log off their machine. This will ensure there is a copy of the user profile on the networked server.
- Get someone with an Admin account to then *delete* the local copy of their user profile from the machine.
- Then the user can log back in and everything functions correctly once more .... until another "reset" becomes necessary. It's often weeks between these resets & we haven't been able to determine the trigger event/s for this, which makes this problem all the more frustrating.
The question:
What I'm looking for is where the corruption might be within their "profile". Is there a folder / file (even if marked hidden) that the logged on user can delete that will clear the apparent corruption (without an Admin doing anything ... it can take a while for an Admin to be available to do this
). The user only has std rights, not Admin.And as a byproduct, just maybe, this area might also be a "cure" for the other Sharepoint "read-only" issue as well
