New Suggested 4/26/2024 by Ryan Vellia

7

votes

FIX CRASHING!!!!

We've been dealing with frequent project crashes since version 9. This needs to be address. Certain projects we make one change, run an equipment evaluation, crash. Make a change, run it again, crash. It is non stop and extremely frustrating! Not only that, after it crashes the projects default to not promoting base changes to other scenarios. So after each crash we have to go and change this setting. Over and over again.

This has been going on for ages, we've shared projects only to never hear back from the Dev team. For software that is 5 figures a seat this should not be happening!

crashing equipment evaluation

John Horak 9/24/2025 12:25 PM

I get crashes about once per 8-16 hours of use. I never get a crash report. Suddenly PTW is just gone. No explanation, no crash report. I have nothing to send to SKM to report what went wrong. Can we get some sort of crash report to explain what went wrong? On the positive side, I have not ever lost more than a few clicks of data input, but on the negative side, it is annoying and I wonder why SKM has not introduced a crash report process to help with their development and improvement process. Maybe they do not want to know and prefer to let POS problems ride.

Ryan Vellia 9/24/2025 12:49 PM

Hey, John. Glad (not for you) I'm not the only one. I agree I don't typically lose too much data either. But if I am creating a report, trying to print multiple crystal reports from multiple scenarios, it can get frustrating quick. For me, if it crashed, after I open the project I have to remember to go manaully re-check the "promote changes to other scenarios" option, otherwise I will lose the changes moving forward.