Excel 2010 64 bit Redim Temporarily Locked Array VBA

Question

Hello All,

I am getting weird temporarily locked array errrors when reinitializing

  redim myarray(0)

After it has been used once. 

I know about the for each/with/goto bugs and they are not relevant here, it is top level.  And only happens in 64 bit, never in 32 bit.  100% VBA.

It looks like one of those horrible memory corruption bugs, where one just needs to randomly change things until it goes away and hope that it does not come back.  But if anyone else has seen this or has ideas what to change that would  be much appreciated.

Runing on Win 8 on VM ware VM.  But should not be relevant.

Anthony

---

Anthony

Answer 1

Hi Anthony,

Thanks for posting in the MSDN Forum.

I think you should show me your code snippet which throw the exception for further research.

On my side I tried it, however it works fine. I'm wondering whether you have some error in your snippet.

Have a good day,

Tom

---

Tom Xu [MSFT]
MSDN Community Support | Feedback to us

Answer 2

Hi Anthony,

Thanks for posting in the MSDN Forum.

I think you should show me your code snippet which throw the exception for further research.

On my side I tried it, however it works fine. I'm wondering whether you have some error in your snippet.

Have a good day,

Tom

---

Tom Xu [MSFT]
MSDN Community Support | Feedback to us

There is no snippet.  It only fails in the totality of the application.   For reasons that are probably unconnected with arrays.   I presume Microsoft has test cases for basic VBA interactions (I hope!!).

If you wanted to play with it, look at arrays redimed in events that are triggered by VBA code.  

That is the problem with these sort of bugs.  They mainly arise as a result of using the horrible C programming language.

My post was just in the vain hope that someone had solved the problem.

Anthony

---

Anthony

Answer 3

Hi Anthony,

I have tried it on my side already, however I never encounter any exceptions like your mentioned. So I ask you to provide some snippet to reproduce your issue. I'm very curious how you encounter this issue if you don't program via VBA code. Do you provide your scenario for further research?

My reproduce environment:

Windows Server 2008 R2, Office 2012 (64-bit).

Have a good day,

Tom

---

Tom Xu [MSFT]
MSDN Community Support | Feedback to us