It happened again: PC-DMIS hung during a Save and wiped away my program, giving me the dreaded PCDLRN serialization error. First time this happened to me in V4.2. It happened weekly in V4.0, monthly in V4.1 WITH the hotfixes installed. And now it happened in V4.2. Be warned, this monster is still lurking out there.
I lost a week of work, because I got so confident with 4.2 that I quit living by my own BACKUP BACKUP BACKUP rules (as many of you know, just saving a program does not shield you from the devastations of this problem). DUMB DUMB DUMB DUMB.OK.
[RANT] This has to be a rant, because clearly Hexagon is unable to see the seriousness of this issue (so I know I can only vent). This issue has been reported now for a year and half and NOTHING is being done about it. It is depressing and rediculous to have to live with this. How can we make this issue into something that Hexagon MUST take notice or takes seriously?
Every time I get this, I get asked to repeat it and I can't. The random nature of this issue is the core of the problem. Once, about a year ago, I figured out how to repeat it and nobody at Hexagon took interest in it. Nobody seemed to care (OK, 1 Hexagon person tried but I never heard from him again). We love to hate the demons, but this is shameful and to be really frank, I am getting fed up with it.
If this problem is so complicated to fix, why not try simple work arounds? For example, take the Silma route to saving programs (create numbered BAK files every time that I save). That would have saved me many days of work... I am sure there are more simple work arounds, that do not fix the problem, but limit the damage when it happens.
HEXAGON: STOP BUYING MORE COMPANIES AND SPEND YOUR MONEY TO FIX THIS PROBLEM NOW!!!!!!!!!!!!!!!!!


[/RANT]
OK Hoedeman, you win.
Jan.
I lost a week of work, because I got so confident with 4.2 that I quit living by my own BACKUP BACKUP BACKUP rules (as many of you know, just saving a program does not shield you from the devastations of this problem). DUMB DUMB DUMB DUMB.OK.
[RANT] This has to be a rant, because clearly Hexagon is unable to see the seriousness of this issue (so I know I can only vent). This issue has been reported now for a year and half and NOTHING is being done about it. It is depressing and rediculous to have to live with this. How can we make this issue into something that Hexagon MUST take notice or takes seriously?
Every time I get this, I get asked to repeat it and I can't. The random nature of this issue is the core of the problem. Once, about a year ago, I figured out how to repeat it and nobody at Hexagon took interest in it. Nobody seemed to care (OK, 1 Hexagon person tried but I never heard from him again). We love to hate the demons, but this is shameful and to be really frank, I am getting fed up with it.
If this problem is so complicated to fix, why not try simple work arounds? For example, take the Silma route to saving programs (create numbered BAK files every time that I save). That would have saved me many days of work... I am sure there are more simple work arounds, that do not fix the problem, but limit the damage when it happens.
HEXAGON: STOP BUYING MORE COMPANIES AND SPEND YOUR MONEY TO FIX THIS PROBLEM NOW!!!!!!!!!!!!!!!!!



[/RANT]

OK Hoedeman, you win.
Jan.
Comment