"Ram�n Jim�nez" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Thinking out loud... > >Then again, I don't know how > they handle this with ad hocs; and using the update database idea, they > could conceivably have an automated way of loading and unloading updates > to reproduce a particular configuration from the update database file. > The problem with ad hoc solutions is that they range from significant code changes to very subtle tweaks. In may cases, they modify behavior that is correct for most but wrong for a few. In some cases they are somewhat goofy. For example, I have my own ad hoc fix to WLD 4.3.10a that makes it work the way I need it to for form submits in our new code. This is supposed to be addressed by WLD 4.3.11 but I have not tested it yet. To recompile my old apps, I need to remove the fix. Clearly, this is not elegant.
Something like the fix above is not going to be addressed by a global update system. By using an ad hoc fix, you are, by definition, doing something to your system that is not ready for prime time. Sometimes, they must be applied in a certain order. All in all, a pretty big deal to try to automate. I don't have a solution. I want the new features but do not want the hassle. Oh well, win a few, lose the rest. -- John Bertoglio Senior Consultant co-laboratory office: 503-538-8691 mobile: 503.330.6713 fax: 503.538.8691 www.co-laboratory.com > > Ram�n
