I remember an issue I had in ProcessBook VBA where code using functions like Left() and Right() suddenly stopped working (VBA did not recognize them as valid functions), but when I replaced them with Left$() and Right$() they worked fine. Perhaps there are different versions of the VBA engine on different machines and that is causing your issue.
Gave this a try, no luck though.
1 of 1 people found this helpful
This is a very strange issue indeed.
The only things I can think of, other than what Steve has said, are:
- has the namespace changed in the AFWrapper code? if you compare the older and the newer wrapper?
- have you registered the required wrapper version correctly? (regasm.exe /codebase afwrapper.dll)
- On a machine where the wrapper does not work, in the VBA editor, if you open tools-->references. Is there any missing reference there?
- You need to make sure to reference to right version for which the ProcessBook file was created with.
- this means you may have to unregister (by using regasm.exe) the afwrapper, and register the version that works with the Processbook file used.
Let us know how it goes,
I haven't found a clear cut solution. After combinations of uninstalling, reinstalling, save displays with missing references, and other odd combinations I can get the displays working. I originally thought the issue would be a GUID issue with the assembly, but everything seemed as it should.
Thanks for the update Alan, I will mark this question as assumed answered for now.
You know where to find us if you have more questions
Thanks for your visit on PI Square!