I have a couple questions which should help me determine what's going on.
1) Is this behavior only occurring within this particular file or does it happen across all displays that have VBA?
2) Do you see any errors before/after the crash?
3) What version of ProcessBook are you using?
Paul - Thanks for the quick response.
- The file is a ProcessBook (.piw) and contains a collection of ~150 displays. Running code on one specific entry/display causes this crash. I can run VBA on other displays within the same book and no issues are seen.
- There are no errors shown.
- I can attach ProcBook.exe in Visual Studio and see the exception but reading assembly is a non-starter.
Event Viewer captured two errors shown below.
Hmm those are some pretty generic looking errors. I think it would probably be best to create a tech support case for this so that someone can hop onto your system and see what's happening. If you want, I can create a tech support case for you (with the information you've provided here) or you can call or email in.
2 of 2 people found this helpful
There is a known issue with the version of ProcessBook you are running which can result into crashes as you experienced them. Please see Known Issue 146197 - ProcessBook Crashes When Closing Unsaved AdHoc Trend Display From PIW Display Opened Directly From Another Display’s Button (the title is longer than the link!)
Can you please update to the current ProcessBook release and see if this is a resolution to your issue?
If this is not the case, we should be connecting you with Technical Support as suggested by Paul.
Updating to the latest PB release did fix the issue. Now it is a waiting game to get this into Production. Thank you for your help.