none
VBA running slow when sprt is debugged by Visual Studio RRS feed

  • Question

  • We run Excel VBA ==> C++ DLL (Visual Studio 2012)

    Previously with Excel 2007, when we want to debug the DLL, we'll attache the VS project to the VBA Sprt first. Then once triggered, VBA will do some processing and call DLL. Then we'll be able to debug C++ dll code in Visual Studio.

    Now when doing the same thing with Excel 2016, while debugged by VS 2012, the above VBA code will run much much slower (maybe 100X times slower?). So it seems Visual Studio C++ now affects VBA's running speed? Which is something unexpected.

    Can someone suggest whether we can avoid this VBA performance issue? (disable some debugging module?)

    thanks a lot.

    Thursday, March 23, 2017 3:36 AM

All replies

  • >> Can someone suggest whether we can avoid this VBA performance issue? (disable some debugging module?)

    Did this issue only exist under VS debugging? If you run VBA directly, will it be slow?

    What do you mean by VBA run much slower? What is the function for VBA code? If you create an empty workbook with simple macro to call this dll, will this issue still exist?


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Friday, March 24, 2017 8:43 AM