T.R | Title | User | Personal Name | Date | Lines |
---|
123.1 | Easy | SHALOT::HUNT | Stop! Or Stallone Will Act Again ... | Thu Feb 27 1992 18:43 | 3 |
| Delete the OA$SITE_DEV_LLV:DEVELOP.FLC file.
Bob Hunt
|
123.2 | Easy II | CESARE::EIJS | All in 1 Piece | Fri Feb 28 1992 08:33 | 4 |
|
And before deleting it, de-install it.
Simon
|
123.3 | Take two happy pills and call me in the morning | A1VAX::BARTH | Bridge-o-matic does it again! | Fri Feb 28 1992 14:05 | 6 |
| And tell them not to precompile DEVELOP any more. I wonder if they
were trying to improve their debugging performance. :^)
Sheesh.
K.
|
123.4 | Programmers are users who deserve respect, too | BUFFER::VICKERS | Winners take action not keep score | Fri Feb 28 1992 22:08 | 13 |
| Those of us who deal with customers regularly realize that a
significant number of them do precompile DEVELOP. While it does seem a
bit silly it isn't that unreasonable especially at sites where forms
stay in DEVELOP for extended periods of time.
I know that Karl doesn't mean to sound like he is assuming to know more
about how to operate the customer's system than does the customer
(there is a smiley face, of course). Doing what is right is to always
listen and understand the customer and their needs before giving them a
lecture about how stupid they are.
Place the customer's needs first,
don
|
123.5 | Always test in the same environment as LIVE | MARVA1::POWELL | Cute But NonDerogatory Personal Name? | Fri Mar 27 1992 19:00 | 10 |
| Another reason DEVELOP is occasionally compiled
is to see if the forms (plural) are going to work COMPILED.
For instance, you can have a formset with > 255 fields work just fine
UNCOMPILED, but move things out of your typical uncompiled DEVELOP
into a live .FLC and watch it stack dump.
Frankly, before going live I put my vote in for testing the forms
in a compiled environment. Same goes for scripts and boilerplates
(which may not break - but may behave differently....)
|