Re: designer reliability was RE: Another Code Oddity

Mike,

> Designer is very reliable, if you do the same thing it will crash the same
> way.  But I'm (slowly) working on changing that, one crashlet at a time.

It is getting better! It's just not quite "there" yet.

> What I don't know if it is the writing to the local file that is
> failing or the transport to the iSeries that is failing.  Maybe I need to
> create an auto-checkpoint  out of the temporary file generated at save
> time.  If you are not seeing any errors at save time then Designer isn't
> detecting any problems but maybe you notice a difference between a "good"
> save and a "bad" one?  Any insight might be helpful...

The save is one of the buggiest parts of it. More often than not, I simply
get that wee little "Saving" dialog box with the counter, but it doesn't do
anything - it just sits there. At that point, I estimate the time it should
take for a save, wait that duration, then click the Cancel button a few
times to clear the dialog box. If I wait long enough, I don't lose changes.


Regards,

John Taylor