The last post regarding Pro/E VB, where the poster had been using Excel VBA and wanted to utilize Pro/E VB, struck a cord with me.
I am in the same situation. But I haven't pursued the move from Excel VBA to Pro/E VB, because of my perception, from other posts to this forum, that the use of Asynch Mode (only mode available to Pro/E VB), is prohibitively slow compared to the Synch Mode, in which JLink can run.
Does anyone have any hard data on the interaction-time penalties one pays with utilizing Asynch Mode vs. Synch Mode, for exchanging information with Pro/E?
I know that we launch Excel VBA programs from Pro/E via Mapkey DOS batch files, and I can tell you that there is often a remarkable delay until Windows opens the program Workbook.
If this is any indication of the delays that one can expect with Asynch Mode, which, I understand, relies on the Windows operating system to pass data between the Pro/E VB program, running in one thread, and Pro/E, running in another thread, then I am not too optimistic regarding the efficacy of Pro/E VB using Asynch Mode.
