The "Null Object" error crash should be easy to find as PB fires the System Error event on your PB App's "Application" object class when anything like this happens. You will see that the System Error event arguments allow you to know the object, method, line number, cause, etc of the System Error.

The key point here is that the PB App codes the System Error event to trap & record the error (like a Null Object) so that the PB developer can then go straight to the faulting line of code and resolve the logic error. Which is typically, a pointer that has not been initialized for some reason.

In the worst case, the PB developers can place an IsValid() around the PowerScipt command that is getting the Null Object error in order to recover from the surrounding code that may not be doing its job correctly (ie such as a CREATE at the right time).

HTH

Chris, thanks. We have the PB app System Error message, but as stated, the System Error crash occurs when doing a specific set of steps, that are not reproducible when the user repeats the steps immediately after restarting our app. My latest question was about what errors in the Event Viewer we should look for. Any suggestion there?



Finally, thanks for the "worst case" suggestion, which I may need to code to get this client by.



Thanks for your help - it's an honor to get advice from you.

Hi Scott;

Since the error does not reoccur on a typical App restart, my guess would be that another process is doing a "Destroy" on a resource that the later executing PowerScript code is depending on (and thinks that its still there). Have a look at your "Destroy xxxx" commands for that resource that gets the Null Object error.

HTH

Regards ... Chris