I work on an app that is totally customized for various clients. I came in a little over a year ago after the app had been around for a number of years.

There are many If's, Cases, etc. all throughout the app for client specific code. I've talked to several people who work in similar situations and they have client specific prgs. Either that way or Kevin's way whould have been preferable, but the app does function.

Things to keep in mind, as Kevin mentioned, do your research to find out if the requested functionality would be beneficial to other clients. If that's the case, make it a system option during setup.

I've worked with another app in the LA area that did have specific client exe's. I talked to a friend who watched them do an install at his location. It was quite comical to watch them try to upgrade his site, then apply the client specific code. It took them 2 days to do the install.

PF

>Here's the picture
>
>We have an application for a vertical market.
>
>Situation that we will be confronted to enventually:
>
>Customer asks for modifications that will apply only fot their business.
>
>Do we tell them that we don't do those or do we do it?
>
>What would be the best way to manage future developments after that customization.
>
>Because after that we'd be stuck with our glocal application but also one (and possibly more if we agree to do those customizations) variations based on our global application.
>
>What would be the best way to manage a possible mess?