1 of 1 people found this helpful
Hello K.T. Huang,
Please accept our apologies for the late reply.
I have just successfully tested ProcessBook 2015R2 SP2 and Excel 365 (Office 365 ProPlus) on Windows 10. Here is what I did:
- Create a new empty workbook and save it as macro-enabled workbook (.xlsm).
- Open the Developer Tab and add an Active-X CommandButton to the first sheet.
- CoubleClick the CommandButton to open the VBA Editor.
- Chose [Tools] -> [References ..] to open the references dialog.
- Add 'PI-ProcessBook Type Library' (%pihome%\Procbook\pbobjlib.tlb) to the list of references.
- Copy your code snippet and paste it to the body of sub CommandButton1_Click() event.
- Exit 'Design Mode' and click the CommandButton.
As a result a new ProcessBook instance was started with a new unsaved PDI named 'Event_evname'.
Can you reproduce this or if not indicate at what step you are experiencing an issue?
I am still getting same popup messages.
Can you please paste a screenshot showing the referenced libraries for your Excel VBA project?