If you remove this folder during sequence there is a registry created that marks this folder c:\temp as #DELETED# which means the folder isn't there anymore. Let's say you for example copy installers into a C:\Temp folder and then start the capture. What happens is when you create an aapsatck and remove an applciation or a file from it, not only is the file removed but also masked as #DELETED#. I believe they stated that this is fixed in version 2.10 but i'll try and explain. I'm guessing that this is the reason it is failing?Īnyone else having success/failure with Visual Basic for Applications? When I do a ProcMon on the appstack it references the snapvolume, which show up as a success however it hits a "HKLM\.Metadata\FS\SVROOT\Program Files (x86)\Common Files\microsoft shared\VBA\VBA7.1\VBE7.DLL\#DETELTED#" and "HKLM\.Metadata\FS\SVROOT\Program Files (x86)\Common Files\microsoft shared\VBA\VBA7.1\VBE7.DLL\SvDeleted" and shows a result of "Name not Found". In doing a procmon while pressing the button I can see that Excel is referencing "C:\Program Files (x86)\Common Files\microsoft shared\VBA\VBA7.1\VBE7.DLL" for VBA in both the registry and the file system, which it is supposed to do, and processing the button.
Visual basic for applications dll install#
If I use the same install and install directly to the capture VM without capturing an appstack then all the buttons in that spreadsheet work without issue. If I install office, 2013 Pro Plus, into an appstack I get a "Can't find file:vba6.dll" issue. We have an Excel spreadsheet that has a few buttons built with Microsoft Visual Basic for Applications.
0 kommentar(er)
