Closed svh1985 closed 3 months ago
Hi @svh1985 ,
Thanks for letting me know!
None of my machines are on ARM so I cannot test. I will try to install a virtual machine when I get some time in the next few weeks and will get back to you.
@svh1985 ,
Is there any chance that you have an addin or different code module that has a LeftB
function defined?
In other words, what kind of error do you get? For example:
or
Hi @cristianbuse,
I read on issue https://github.com/cristianbuse/VBA-FileTools/issues/21 that the user was running on Win11 ARM too, and only had a minor unrelated issue. So, I figured something else might be wrong in my case. Therefore, I compared the references of an empty Excel file with my project and did some corrections. And it seems to be work now!
Thanks for helping out, and your efforts on this project!
Ps. I think ARM can be added to the list supported CPU’s. 🎉
@svh1985 Curious what references had to be added. No idea why I'm getting notifications for this, but I'm also working on some vba with ARM as a target so would be interested to know approx what you did :)
Many thanks @svh1985 for your feedback!
I am also curious what references were causing the issue.
Also, please download the latest version, I just pushed a minor change based on latest OneDrive version.
Hi there,
I'm running the ARM version of Windows & Office and my Excel projects using the VBA-FileTools are showing a lot of errors. While I'm doing my best to fix them, I'm not a VBA expert.
Hoping to get some tips and support!
One thing I noticed is that a lot of VBA functions need to be changed. Example: LeftB$ changed to VBA.LeftB$.
Thanks!