Update of old apps

[Roger Eller]

If the changes are to help you to work more efficiently, I would simply
make them aware of that fact just in-case something breaks.  I would not
charge for the added work unless it benefits the customer, and they have
asked for it.  My 2 cents.

~Roger


On Wed, Jul 16, 2014 at 8:41 AM, <jbv at souslelogo.com> wrote:

> ok I get it, thanks for the advice...
> But still my main worry is rather about aging code that could be
> replaced by new LC features that would save time & energy in
> future updates/maintenance...
> I am not going to clutter the list about it, but I'm really wondering
> about that.
>
> Best,
> jbv
>
>
> > I agree with Richmond.  In my experience, it is wise to use the version
> > the
> > app was originally coded in.  Too many times when I've used the latest,
> > everything looks great until the customer comes across that one thing,
> > rarely used, that no longer works because you need to code it just
> > slightly
> > different in the new version.
> >
> > ~Roger
>
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>