In the interest of providing more information, it should be noted that things work fine, on multiple computers, but not on multiple others. I have not been able to figure out what makes the computers, on which the error occurs, substantively different from the ones on which the error does not occur, but I don't believe it's an issue of x86 vs. x64.
TurboActivate.Init Causing Error, When Workbook OpensAnswered
I followed your instructions to use TurboActivate with my Excel workbook, using VBA, and it all worked just fine. Then, I tried copying the workbook, and all other related TurboActivate files (i.e., DLLs, forms, etc.) to a folder, on another computer. Then, when I tried to open the workbook on the other computer, an error was raised (something about an function invalid call or argument or something). I have determined that the error is occurring, when the Init method of the TurboActivate class is executed, as shown in last code line below:
' Create the new TurboActivate instance Dim ta As TurboActivate Set ta = New TurboActivate
On Error GoTo TAProcError
' Grab the GUID, from the version page, for this workbook/product, at LimeLM, and paste it below. Call ta.Init("3k3vi2kqspjzqb7p6jegdinfowphuvq")
I can then go to the Visual Basic code, once the workbook is open, and after the error message, and run the same code and it works fine. In other words, when the code executes, when the workbook opens, I get an error, but, when I manually execute the code, after the workbook already opened, it works just fine.
What could be causing this issue? I can send the actual workbook, if it would help, as long as you tell me how to send it, as I can't see a way to attach files to this question/post.
Answer
Step 3b and 4 cover where the TurboActivate dynamic library should be put.
What error are you getting?
Add breakpoints to your code.
What are the exact lines of code that are failing (yes, the Init call, but dig in deeper than that – follow the function call and see what inside the Init call is failing).
Breakpoints are your friend.
Invalid Procedure Call Or Argument (Error 5) is what occurs. However, it only occurs, when initially opening the workbook. When running code, after workbook loads, manually, it works fine, with no errors.
Breakpoints aren't helpful, as they don't persist, when closing the workbook. I could put in a Stop command, within the Init function, or right before the call to it, but I'm not sure that will help, as then the workbook will have loaded fully, before the code is executed.
I just don't understand why the code runs just fine, if I run it, after the workbook loads, but it gets the above error, if it runs when the workbook is loading.
If you can't add breakpoints (or figure out how to pause the code long enough so that you can add breakpoints) then you should add debugging statements that output exactly what functions are called, the parameters being passed in, error codes being returned, etc.
Then, go from there. (Find exactly what line of code is failing, why it's failing, a fix that problem).