Excel 2010 VBA 7 Macro on 2008 R2 Citrix - Cannot Lock Memory
This is merely a theory at this point but I have a scenario where the customer switched from Reflections to Rumba and give a set of instructions to open Reflection session, select Macro, Visual Basic Editor, Open each module, class, and form file in Reflection and export it to an external file within your project folder, Copy the Rumba migration spreadsheet template to your project folder and rename it, open the spreadsheet, select Developer Tab, click Visual Basic, enter project name, import the code just exported from Reflection, import all modules from initial folder, add all elements, repeat until all modules, forms, and classes imported. This is abridged version.
My concern is for the customers (end-users) at this point. These instructions were performed on a Windows 7 32-Bit operating system running Office 2010 32-Bit. Using one example, UserA has 200 of these new XLMS macro saved Excel files. All of them have base modules and call Rumba Interface.