I see script disappearing frequently from my applications. Frequently I’ll get a compile error at run time (should be impossible) because End or Next statements are dropped when a form is saved. Also, I notice that there is enormous instability in hide/when formulas in R6 - just like the bad old days in R4 when they would, on their own, shift up a position in the form and be totally inappropriate.
Thus far, while I like some of the new tools in R6, I’m disgusted by the behavior of Designer and if I had my way I’d go back to R5 in a heartbeat. Sadly, though, that isn’t an option where I’m now employed and I have to make do.
IBM/Lotus/Iris, are you listening? It’s happening to just about everyone in R6 that I’ve talked to and it’s incredibly aggravating.
It just vanishes - you have no warning, no indication of anything amiss until you try to load the application from your client - sometimes you get obvious compile errors from dropped loop or conditional statements, in other cases I have noticed entire paragraphs or even an entire function totally missing.
Yesterday, I tried to delete a bunch of functions and subs that I had in the Globals of a form. When I tried that, it wouldn’t drop the Exit Sub or Exit function statement and I had “ghosts” of all the subs and functions in the form and of course it wouldn’t save.
Another thing I see, which may be specific to me, is when I use the bright red font in fields. If I have multiple red fields on a line, and then go between them and hit the return key to give a line break, all the fields subsequent to the break revert to black text. When you click on the field properties, however, it still shows as being allegedly red text.
I could go on and on, but the bottom line is that the behavior of Designer is aberrant and unpredictable. I have little confidence that what I code today will make it to tomorrow 100% as I coded it. Needless to say, this drags development time out and leaves me very frustrated.
What I believe is that there are some buggy elements in Designer which can induce corruption in design notes. Depending upon how you code your design elements, you may or may not run across them and therefore this is a fairly spotty thing and is hard to reproduce since the behavior is so intermittent and unpredictable.
Oh, just for information’s sake, I’m running ND6.01 CF1 on a Win2k platform - pretty generic, I’d say.
I saw a post not long ago where a Lotus person announced they found at least one of the causes of this bug and expected it to be fixed in the January 2004 release.
I found a post a while ago which seems to have stopped this for me (most of the time - not all)in the designer, on the Programmer Pane Properties dialog, on the propeller-hat tab, unselect